On Sat, 18 Oct 2003, codemastr wrote:

> Just wondering about this. Like the TODO list says, using stdin is bad for a
> library (especially with Windows where stdin might do nothing in a GUI app,
> or even on *nix with a forked() program). What I'm wondering is, what about
> doing something where the user can specify an input fd? Like a
> CURLOPT_TELNETINPUTFD or something (well I guess that'd actually be a FILE
> *, but same idea)?

If I were to write a simple telnet client, I wouldn't want that. I would
rather prefer to get data received to me in the write callback, and when I
want to send data I'd prefer to have some kind of "send" function. It wouldn't
even have to involve any file descriptors or FILE pointers.

However, I don't think we should focus very much on fiddling with TELNET and
the telnet code right now, since very few users are actually using libcurl to
do telnet stuff. I think we can leave the current code as it is, and focus on
the improvements once we know that there's at least one eager user who
needs/wants them.

PS. earlier today I made the KNOWN_BUGS document appear as a web page on the
curl site: http://curl.haxx.se/docs/knownbugs.html

-- 
 Daniel Stenberg -- curl: been grokking URLs since 1998
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise 
Linux in the Boardroom; in the Front Office; & in the Server Room 
http://www.enterpriselinuxforum.com