On Sat, Nov 22, 2008 at 02:46:56PM +0530, Kulanthaivel wrote:
> Currently I am porting curllib to a proprietary ARM platform. In this platform
> I have only asynchronous sockets in which all the socket events (Connect, Read,
> Write and Close) are notified via events. As for my understanding the the
> current curllib implementation expects the socket to be synchronous or blocking
> at certain levels (At least for connecting). Can anyone suggest me some idea or
> specific places/modules/functions where I can start customizing curllib to
> support asynchronous sockets.

If your application don't actually require nonblocking sockets you could
just emulate a blocking socket interface by waiting for the completion
event after every operation. That's simple and depending on your application
may be good enough. Otherwise, there was a discussion here about asynchronous
sockets some months ago--try looking through the archives.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved