Thanks for your reply, BTW I am not in urgency to delete Windows code and then implement again using NSS ;), I have started the Linux development using NSS. I am glade to hear that other people are also working on that module, its really help if they keep this discussion going on. I am waiting for the replies specialy from Michael Moss as you mentioned he worked on this module.
On Wed, Sep 10, 2008 at 6:42 AM, Dan Kegel <[EMAIL PROTECTED]> wrote: > > On Wed, Sep 10, 2008 at 2:53 AM, Ibrar Ahmed <[EMAIL PROTECTED]> > wrote: > > I am currently working on porting "ssl_client_socket" to Linux. The > current > > implementation of "ssl_client_socket" uses Windows Security API. I wonder > > why we have not used NSS library to implement SSL socket in Windows, > because > > it is available to many OS. I am not very good in Windows specific API's > :( > > > > If there is no reason of doing this, should I rewrite this class again > using > > NSS and remove the Windows specific implemnation. If there are reason of > > doing this can someone list here? > > Sounds like a fine idea, but get it working in Linux before worrying about > replacing the Windows code... > > The --new-http option is the way things are headed on Windows, btw. > > BTW, Michael Moss was working on getting nss included in the > linux build, and somebody else fairly serious was already looking at using > it, > hopefully they will chime in here. > - Dan > > > > -- -- Ibrar Ahmed EnterpriseDB http://www.enterprisedb.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
