Fred Covely wrote:
>I asked a similar question (although not exactly the same), a couple of days
>ago. Mine
>was 'is netlib' suitable for server side applications? The response I got
>was 'no, its
>really a client side library and limits connections to 50.' This thread
>indicates it would
>be acceptable given that the implementation handles the threading issue.
>
>I'm (as usual) confused. Can someone clarify.
>
>While anyone is at it, care to offer a comparison of netlib, libwww, and
>ACE?
>
>regards,
>F. Covely
>
>
>"Naveen" <[EMAIL PROTECTED]> wrote in message
>95a212$[EMAIL PROTECTED]">news:95a212$[EMAIL PROTECTED]...
>
>>I would like to use netlib as a library in one of our server components, I
>>just some doubts abt the library like
>>1. Can u we use it as a standalone. Is it a lot of work to use that as a
>>standalone?
>>
necko depends on nspr, xpcom, libpref (which requires many other
libraries as well including mozjs). we are hoping to one day break our
dependency on libpref.
>>
>>2. Is the library multithreaded , i.e can we have multiple HTTP, FTP
>>downloads at the same time.
>>
necko is not entirely thread safe. this does not preclude you from
having multiple HTTP, FTP, etc. downloads at the same time. we use a
single main thread with an event queue. all protocol processing happens
on this event queue. we use a worker thread for all socket i/o (this
thread blocks on PR_Poll) and we use 1-4 worker threads for reading files.
we are working toward making HTTP callable from multiple threads...
sadly this is currently not an option :-(
darin
>>
>>
>>Any help will be appreciated.
>>
>>Thank you in advance.
>>
>>
