I opened a ticket for this at
http://bugzilla.gnome.org/show_bug.cgi?id=372013
with some links to mingw-friendly implementations
of nonblocking connections, but I'm pretty busy.
If someone wants to make a patch, though, I'd be happy
to accept it.
Charles
robert mcdonald wrote:
> You're correct. And the windows variant of the code is
> extremely similar (trivial differences) and works
> equally well.
>> On 11/6/06, Charles Kerr <address@hidden>
>> wrote:
>>> The socket creation code is a special case there
>> -- it's the /only/
>>> part of Pan that uses threads, and it's a very
>> small task. The
>>> purpose here is to make a connection in a
>> nonblocking way so that
>>> Pan doesn't freeze while connecting.
>> Humh... As I remember, it is possible to make a
>> socket connection
>> non-blocking without using threads. I have done such
>> thing with select
>> (or poll). The algo: create the socket and connect
>> it (O_NONBLOCK),
>> then register the file descriptor in select (poll)
>> and then, when
>> something occurs, it is probably a connection
>> success (or failure).
>> Look at
>>
> http://www.developerweb.net/forum/showthread.php?p=13486
>> Perhaps it could be interesting to rewrite the
>> "connection" part, so
>> pan will be fully thread safe (which is more simpler
>> and safer than
>> multi-thread). I'm quite sure that such asynchronous
>> connection could
>> be made with the GLIB "event loop".
>>
>> What's your opinion? Do you already try such
>> asynchronous connection?
_______________________________________________
Pan-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/pan-devel