From rajeev.sebastian at gmail.com Sat Dec 1 08:51:46 2007 From: rajeev.sebastian at gmail.com (Rajeev J Sebastian) Date: Sat, 1 Dec 2007 22:21:46 +0530 Subject: [Jslib] Reading available data on recently closed sockets In-Reply-To: References: Message-ID: <79a035420712010851g34e99da8i5171685aa4b474cd@mail.gmail.com> Hello Nick, On Dec 1, 2007 4:33 AM, Nick P wrote: > I am still attempting to use JSLib as a client for a server. After the > server sends a reply message, it closes the socket. Up until the socket is > closed by the server, the XUL client recognizes that there is data > available. When I built a sample client in VB.net, I was able to read the > available data even after the server closed the socket. However, with the > JSLib sockets, I have been unable to get it to read the data after the > server closes the socket. > > Am I wrong that this data should still be available for reading, or is this > unexpected behavior? I ran the equivalent with Python, and I can reproduce the above behaviour. I used a Python based socket server and client.(based on http://docs.python.org/lib/socket-example.html, only the server closes the client after receving three times) With (unmodified) socket.xul, it just gives a message that the socket was closed. However, with the Python client, it returns the data. I havent done any extensive testing or anythign ... just a 15 minute job. Regards Rajeev J Sebastian From nick.pend at gmail.com Sat Dec 1 20:40:58 2007 From: nick.pend at gmail.com (Nick P) Date: Sat, 1 Dec 2007 23:40:58 -0500 Subject: [Jslib] Reading available data on recently closed sockets In-Reply-To: <79a035420712010851g34e99da8i5171685aa4b474cd@mail.gmail.com> References: <79a035420712010851g34e99da8i5171685aa4b474cd@mail.gmail.com> Message-ID: Thanks for the confirmation Rajeev. Pete (or anyone in the know here) - I don't know if you have time to look at this -- if you don't, but you could tell me some functions to start looking in in the library itself, I'll take a look. I know very little about XPCOM but I might be able to turn something up. If I can clarify better let me know - in short, after a server sends data to a XUL/JS client, it closes a socket. Instead of the JSLib client still being able to read the data that was sent to its socket, it sees zero bytes. Expected behavior should be (I believe) that it can still read the data that was made available to it. Thanks, Nick On Dec 1, 2007 11:51 AM, Rajeev J Sebastian wrote: > Hello Nick, > > On Dec 1, 2007 4:33 AM, Nick P wrote: > > I am still attempting to use JSLib as a client for a server. After the > > server sends a reply message, it closes the socket. Up until the socket > is > > closed by the server, the XUL client recognizes that there is data > > available. When I built a sample client in VB.net, I was able to read > the > > available data even after the server closed the socket. However, with > the > > JSLib sockets, I have been unable to get it to read the data after the > > server closes the socket. > > > > Am I wrong that this data should still be available for reading, or is > this > > unexpected behavior? > > I ran the equivalent with Python, and I can reproduce the above behaviour. > > I used a Python based socket server and client.(based on > http://docs.python.org/lib/socket-example.html, only the server closes > the client after receving three times) > > With (unmodified) socket.xul, it just gives a message that the socket > was closed. However, with the Python client, it returns the data. > > I havent done any extensive testing or anythign ... just a 15 minute job. > > Regards > Rajeev J Sebastian > _______________________________________________ > Jslib mailing list > Jslib at mozdev.org > https://www.mozdev.org/mailman/listinfo/jslib > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.mozdev.org/pipermail/jslib/attachments/20071201/60cb3aeb/attachment.html From rajeev.sebastian at gmail.com Sun Dec 2 10:12:06 2007 From: rajeev.sebastian at gmail.com (Rajeev J Sebastian) Date: Sun, 2 Dec 2007 23:42:06 +0530 Subject: [Jslib] Reading available data on recently closed sockets In-Reply-To: References: <79a035420712010851g34e99da8i5171685aa4b474cd@mail.gmail.com> Message-ID: <79a035420712021012w404d6530j904dda0c09b8d10b@mail.gmail.com> Hello Nick, I made a couple of changes to network/socket.js and samples/socket.xul ... I _believe_ it works with the socket server example that I had used when testing with the Python client as I mentioned before. I am attaching the socket.js and socket.xul with this email. Sorry, I dont remember how to use CVS and I didnt think to maintain a pristine copy of jslib before making the changes, so I dont have diffs. :/ I am also attaching the sample Python server/client with this email. Meanwhile, i will give the testing one more go, just to make sure it actually does work. Could you also verify it works with your example ? Regards Rajeev J Sebastian On Dec 2, 2007 10:10 AM, Nick P wrote: > Thanks for the confirmation Rajeev. > > Pete (or anyone in the know here) - I don't know if you have time to look > at this -- if you don't, but you could tell me some functions to start > looking in in the library itself, I'll take a look. I know very little > about XPCOM but I might be able to turn something up. > > If I can clarify better let me know - in short, after a server sends data to > a XUL/JS client, it closes a socket. Instead of the JSLib client still > being able to read the data that was sent to its socket, it sees zero bytes. > Expected behavior should be (I believe) that it can still read the data that > was made available to it. > > Thanks, > Nick > > > > On Dec 1, 2007 11:51 AM, Rajeev J Sebastian > wrote: > > > > > > > > Hello Nick, > > > > > > On Dec 1, 2007 4:33 AM, Nick P wrote: > > > I am still attempting to use JSLib as a client for a server. After the > > > server sends a reply message, it closes the socket. Up until the socket > is > > > closed by the server, the XUL client recognizes that there is data > > > available. When I built a sample client in VB.net, I was able to read > the > > > available data even after the server closed the socket. However, with > the > > > JSLib sockets, I have been unable to get it to read the data after the > > > server closes the socket. > > > > > > > > Am I wrong that this data should still be available for reading, or is > this > > > unexpected behavior? > > > > I ran the equivalent with Python, and I can reproduce the above behaviour. > > > > I used a Python based socket server and client.(based on > > http://docs.python.org/lib/socket-example.html, only the server closes > > the client after receving three times) > > > > With (unmodified) socket.xul , it just gives a message that the socket > > was closed. However, with the Python client, it returns the data. > > > > I havent done any extensive testing or anythign ... just a 15 minute job. > > > > Regards > > Rajeev J Sebastian > > _______________________________________________ > > Jslib mailing list > > Jslib at mozdev.org > > https://www.mozdev.org/mailman/listinfo/jslib > > > > > _______________________________________________ > Jslib mailing list > Jslib at mozdev.org > https://www.mozdev.org/mailman/listinfo/jslib > > -------------- next part -------------- A non-text attachment was scrubbed... Name: jslib_socket_test.zip Type: application/zip Size: 5162 bytes Desc: not available Url : http://www.mozdev.org/pipermail/jslib/attachments/20071202/e5265695/attachment.zip From nick.pend at gmail.com Mon Dec 3 11:16:02 2007 From: nick.pend at gmail.com (Nick P) Date: Mon, 3 Dec 2007 14:16:02 -0500 Subject: [Jslib] Reading available data on recently closed sockets In-Reply-To: <79a035420712021012w404d6530j904dda0c09b8d10b@mail.gmail.com> References: <79a035420712010851g34e99da8i5171685aa4b474cd@mail.gmail.com> <79a035420712021012w404d6530j904dda0c09b8d10b@mail.gmail.com> Message-ID: Rajeev, I can confirm that this does work - I replaced my socket.js with your edited version. A diff shows these changes: C:\Program Files\GnuWin32\bin>diff "C:\Program Files\Mozilla Firefox\chrome\jslib\network\socket.js" "C:\Program Files\Mozilla Firefox\chrome\jslib\network\socket.js.old" 25,26c25,26 < // if (!this.isAlive()) < // return 0; --- > if (!this.isAlive()) > return 0; 219,220c219,220 < if (!this.available()) < throw "Socket.read: Nothing available."; --- > if (!this.isAlive()) > throw "Socket.read: Not Connected."; C:\Program Files\GnuWin32\bin> ------------------ So now, the Receive works as one would expect. The call from available in the demo still shows zero bytes - but this is probably because it calls isAlive before it calls available. It would make sense to change the demo so that the Available button would show the new functionality, although I haven't tested this. FYI, this is the demo's function call for the Available? button function availableSocket( theSocket ) { statusMsg.value = ( theSocket.isAlive() ? "socket has " + theSocket.available() + " bytes pending" : "socket is not connected" ); } Pete, I hope you can use this. Thanks Rajeev! nick On Dec 2, 2007 1:12 PM, Rajeev J Sebastian wrote: > Hello Nick, > > I made a couple of changes to network/socket.js and samples/socket.xul ... > > I _believe_ it works with the socket server example that I had used > when testing with the Python client as I mentioned before. > > I am attaching the socket.js and socket.xul with this email. > > Sorry, I dont remember how to use CVS and I didnt think to maintain a > pristine copy of jslib before making the changes, so I dont have > diffs. :/ > > I am also attaching the sample Python server/client with this email. > > Meanwhile, i will give the testing one more go, just to make sure it > actually does work. > > Could you also verify it works with your example ? > > Regards > Rajeev J Sebastian > > On Dec 2, 2007 10:10 AM, Nick P wrote: > > Thanks for the confirmation Rajeev. > > > > Pete (or anyone in the know here) - I don't know if you have time to > look > > at this -- if you don't, but you could tell me some functions to start > > looking in in the library itself, I'll take a look. I know very little > > about XPCOM but I might be able to turn something up. > > > > If I can clarify better let me know - in short, after a server sends > data to > > a XUL/JS client, it closes a socket. Instead of the JSLib client still > > being able to read the data that was sent to its socket, it sees zero > bytes. > > Expected behavior should be (I believe) that it can still read the data > that > > was made available to it. > > > > Thanks, > > Nick > > > > > > > > On Dec 1, 2007 11:51 AM, Rajeev J Sebastian > > wrote: > > > > > > > > > > > > Hello Nick, > > > > > > > > > On Dec 1, 2007 4:33 AM, Nick P wrote: > > > > I am still attempting to use JSLib as a client for a server. After > the > > > > server sends a reply message, it closes the socket. Up until the > socket > > is > > > > closed by the server, the XUL client recognizes that there is data > > > > available. When I built a sample client in VB.net, I was able to > read > > the > > > > available data even after the server closed the socket. However, > with > > the > > > > JSLib sockets, I have been unable to get it to read the data after > the > > > > server closes the socket. > > > > > > > > > > > Am I wrong that this data should still be available for reading, or > is > > this > > > > unexpected behavior? > > > > > > I ran the equivalent with Python, and I can reproduce the above > behaviour. > > > > > > I used a Python based socket server and client.(based on > > > http://docs.python.org/lib/socket-example.html, only the server closes > > > the client after receving three times) > > > > > > With (unmodified) socket.xul , it just gives a message that the socket > > > was closed. However, with the Python client, it returns the data. > > > > > > I havent done any extensive testing or anythign ... just a 15 minute > job. > > > > > > Regards > > > Rajeev J Sebastian > > > _______________________________________________ > > > Jslib mailing list > > > Jslib at mozdev.org > > > https://www.mozdev.org/mailman/listinfo/jslib > > > > > > > > > _______________________________________________ > > Jslib mailing list > > Jslib at mozdev.org > > https://www.mozdev.org/mailman/listinfo/jslib > > > > > > _______________________________________________ > Jslib mailing list > Jslib at mozdev.org > https://www.mozdev.org/mailman/listinfo/jslib > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.mozdev.org/pipermail/jslib/attachments/20071203/81acf957/attachment.html From nick.pend at gmail.com Mon Dec 3 11:21:10 2007 From: nick.pend at gmail.com (Nick P) Date: Mon, 3 Dec 2007 14:21:10 -0500 Subject: [Jslib] JSLib intermittently does not work in Firefox - reinstall fixes Message-ID: This happened to me once, and I wrote it off as a fluke, but now it happened again and I want to ask if anyone else has seen this behavior before. I installed JSLib, and used it successfully. Some time later, I loaded Firefox and none of my JSLib .xul examples would load. jslib:about and other commands did not work - but jslib:docs did take me to the on-line documentation. Restarting Firefox did not fix the problem, and I believe I even rebooted and it did not fix the problem. Each time I re-installed JSLib, rebooted, and it worked. Let me know if you can explain this behavior or if you can recommend me to look for anything the next time it happens. Windows XP/ Firefox 2.0, using *jslib_current_static.xpi. Thanks, Nick * -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.mozdev.org/pipermail/jslib/attachments/20071203/df8c7a1c/attachment.html From nick.pend at gmail.com Mon Dec 3 11:46:09 2007 From: nick.pend at gmail.com (Nick P) Date: Mon, 3 Dec 2007 14:46:09 -0500 Subject: [Jslib] Reading available data on recently closed sockets In-Reply-To: References: <79a035420712010851g34e99da8i5171685aa4b474cd@mail.gmail.com> <79a035420712021012w404d6530j904dda0c09b8d10b@mail.gmail.com> Message-ID: I forgot to mention the relevant changes that Rajeev did make to socket.xul. C:\Program Files\GnuWin32\bin>diff "C:\Program Files\Mozilla Firefox\ 63a64,65 > if( bytesAvailable > 0 ) > { 66,70c68,71 < socketData.length; < if (!theSocket.isConnected) < { < socketResults.value = "the socket is closed"; < } --- > socketData.length; > } > else > socketResults.value = "the socket is closed"; On Dec 3, 2007 2:16 PM, Nick P wrote: > Rajeev, > > I can confirm that this does work - I replaced my socket.js with your > edited version. A diff shows these changes: > > C:\Program Files\GnuWin32\bin>diff "C:\Program Files\Mozilla > Firefox\chrome\jslib\network\socket.js" "C:\Program Files\Mozilla > Firefox\chrome\jslib\network\socket.js.old" > 25,26c25,26 > < // if (!this.isAlive()) > < // return 0; > --- > > if (!this.isAlive()) > > return 0; > 219,220c219,220 > < if (!this.available()) > < throw " Socket.read: Nothing available."; > --- > > if (!this.isAlive()) > > throw "Socket.read: Not Connected."; > > C:\Program Files\GnuWin32\bin> > > ------------------ > So now, the Receive works as one would expect. The call from available in > the demo still shows zero bytes - but this is probably because it calls > isAlive before it calls available. It would make sense to change the demo > so that the Available button would show the new functionality, although I > haven't tested this. FYI, this is the demo's function call for the > Available? button > > function availableSocket( theSocket ) > { > statusMsg.value = ( theSocket.isAlive() > ? "socket has " + theSocket.available() + " bytes pending" > : "socket is not connected" ); > } > > > Pete, I hope you can use this. > > Thanks Rajeev! > > nick > > On Dec 2, 2007 1:12 PM, Rajeev J Sebastian > wrote: > > > Hello Nick, > > > > I made a couple of changes to network/socket.js and samples/socket.xul > > ... > > > > I _believe_ it works with the socket server example that I had used > > when testing with the Python client as I mentioned before. > > > > I am attaching the socket.js and socket.xul with this email. > > > > Sorry, I dont remember how to use CVS and I didnt think to maintain a > > pristine copy of jslib before making the changes, so I dont have > > diffs. :/ > > > > I am also attaching the sample Python server/client with this email. > > > > Meanwhile, i will give the testing one more go, just to make sure it > > actually does work. > > > > Could you also verify it works with your example ? > > > > Regards > > Rajeev J Sebastian > > > > On Dec 2, 2007 10:10 AM, Nick P < nick.pend at gmail.com> wrote: > > > Thanks for the confirmation Rajeev. > > > > > > Pete (or anyone in the know here) - I don't know if you have time to > > look > > > at this -- if you don't, but you could tell me some functions to start > > > > > looking in in the library itself, I'll take a look. I know very > > little > > > about XPCOM but I might be able to turn something up. > > > > > > If I can clarify better let me know - in short, after a server sends > > data to > > > a XUL/JS client, it closes a socket. Instead of the JSLib client > > still > > > being able to read the data that was sent to its socket, it sees zero > > bytes. > > > Expected behavior should be (I believe) that it can still read the > > data that > > > was made available to it. > > > > > > Thanks, > > > Nick > > > > > > > > > > > > On Dec 1, 2007 11:51 AM, Rajeev J Sebastian > > > > > wrote: > > > > > > > > > > > > > > > > Hello Nick, > > > > > > > > > > > > On Dec 1, 2007 4:33 AM, Nick P wrote: > > > > > I am still attempting to use JSLib as a client for a server. > > After the > > > > > server sends a reply message, it closes the socket. Up until the > > socket > > > is > > > > > closed by the server, the XUL client recognizes that there is data > > > > > > > available. When I built a sample client in VB.net, I was able to > > read > > > the > > > > > available data even after the server closed the socket. However, > > with > > > the > > > > > JSLib sockets, I have been unable to get it to read the data after > > the > > > > > server closes the socket. > > > > > > > > > > > > > > Am I wrong that this data should still be available for reading, > > or is > > > this > > > > > unexpected behavior? > > > > > > > > I ran the equivalent with Python, and I can reproduce the above > > behaviour. > > > > > > > > I used a Python based socket server and client.(based on > > > > http://docs.python.org/lib/socket-example.html, only the server > > closes > > > > the client after receving three times) > > > > > > > > With (unmodified) socket.xul , it just gives a message that the > > socket > > > > was closed. However, with the Python client, it returns the data. > > > > > > > > I havent done any extensive testing or anythign ... just a 15 minute > > job. > > > > > > > > Regards > > > > Rajeev J Sebastian > > > > _______________________________________________ > > > > Jslib mailing list > > > > Jslib at mozdev.org > > > > https://www.mozdev.org/mailman/listinfo/jslib > > > > > > > > > > > > > _______________________________________________ > > > Jslib mailing list > > > Jslib at mozdev.org > > > https://www.mozdev.org/mailman/listinfo/jslib > > > > > > > > > > _______________________________________________ > > Jslib mailing list > > Jslib at mozdev.org > > https://www.mozdev.org/mailman/listinfo/jslib > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.mozdev.org/pipermail/jslib/attachments/20071203/61ca8dc6/attachment-0001.html From pete at mozdevgroup.com Mon Dec 3 13:37:31 2007 From: pete at mozdevgroup.com (Pete Collins) Date: Mon, 03 Dec 2007 14:37:31 -0700 Subject: [Jslib] JSLib intermittently does not work in Firefox - reinstall fixes In-Reply-To: References: Message-ID: <4754771B.2010305@mozdevgroup.com> Is it possible you have two jslib's installed? One in global chrome c:\Program Files\Firefox\chrome\jslib and one in your user profile dir? --pete Nick P wrote: > This happened to me once, and I wrote it off as a fluke, but now it > happened again and I want to ask if anyone else has seen this behavior > before. > > I installed JSLib, and used it successfully. Some time later, I > loaded Firefox and none of my JSLib .xul examples would load. > jslib:about and other commands did not work - but jslib:docs did take > me to the on-line documentation. Restarting Firefox did not fix the > problem, and I believe I even rebooted and it did not fix the > problem. Each time I re-installed JSLib, rebooted, and it worked. > > Let me know if you can explain this behavior or if you can recommend > me to look for anything the next time it happens. > > Windows XP/ Firefox 2.0, using * *jslib_current_static.xpi* > > . > > Thanks, > Nick > * > >------------------------------------------------------------------------ > >_______________________________________________ >Jslib mailing list >Jslib at mozdev.org >https://www.mozdev.org/mailman/listinfo/jslib > > -- Pete Collins - Founder, Mozdev Group Inc. www.mozdevgroup.com Mozilla Software Development Solutions tel: 1-719-302-5811 fax: 1-719-302-5813 From rajeev.sebastian at gmail.com Mon Dec 3 14:35:03 2007 From: rajeev.sebastian at gmail.com (Rajeev J Sebastian) Date: Tue, 4 Dec 2007 04:05:03 +0530 Subject: [Jslib] Reading available data on recently closed sockets In-Reply-To: References: <79a035420712010851g34e99da8i5171685aa4b474cd@mail.gmail.com> <79a035420712021012w404d6530j904dda0c09b8d10b@mail.gmail.com> Message-ID: <79a035420712031435u2a9bbd48vf5459b610b857e62@mail.gmail.com> Hello Pete, Is it possible to have mercurial access to the jslib repository in some standard way ? Does jslib still use CVS ? Regards Rajeev J Sebastian On Dec 4, 2007 1:16 AM, Nick P wrote: > I forgot to mention the relevant changes that Rajeev did make to socket.xul. > > > C:\Program Files\GnuWin32\bin>diff "C:\Program Files\Mozilla Firefox\ > 63a64,65 > > if( bytesAvailable > 0 ) > > { > 66,70c68,71 > < socketData.length; > < if (!theSocket.isConnected) > < { > < socketResults.value = "the socket is closed"; > < } > --- > > socketData.length; > > } > > else > > socketResults.value = "the socket is closed"; > > > > On Dec 3, 2007 2:16 PM, Nick P wrote: > > Rajeev, > > > > I can confirm that this does work - I replaced my socket.js with your > edited version. A diff shows these changes: > > > > C:\Program Files\GnuWin32\bin>diff "C:\Program Files\Mozilla > Firefox\chrome\jslib\network\socket.js" "C:\Program Files\Mozilla > Firefox\chrome\jslib\network\socket.js.old" > > 25,26c25,26 > > < // if (!this.isAlive()) > > < // return 0; > > --- > > > if (!this.isAlive()) > > > return 0; > > 219,220c219,220 > > < if (!this.available()) > > < throw " Socket.read: Nothing available."; > > --- > > > if (!this.isAlive()) > > > throw "Socket.read: Not Connected."; > > > > C:\Program Files\GnuWin32\bin> > > > > ------------------ > > So now, the Receive works as one would expect. The call from available in > the demo still shows zero bytes - but this is probably because it calls > isAlive before it calls available. It would make sense to change the demo > so that the Available button would show the new functionality, although I > haven't tested this. FYI, this is the demo's function call for the > Available? button > > > > function availableSocket( theSocket ) > > { > > statusMsg.value = ( theSocket.isAlive() > > ? "socket has " + theSocket.available() + " bytes pending" > > : "socket is not connected" ); > > } > > > > > > Pete, I hope you can use this. > > > > Thanks Rajeev! > > > > nick > > > > > > > > > > On Dec 2, 2007 1:12 PM, Rajeev J Sebastian < rajeev.sebastian at gmail.com > > wrote: > > > > > Hello Nick, > > > > > > I made a couple of changes to network/socket.js and samples/socket.xul > ... > > > > > > I _believe_ it works with the socket server example that I had used > > > when testing with the Python client as I mentioned before. > > > > > > I am attaching the socket.js and socket.xul with this email. > > > > > > Sorry, I dont remember how to use CVS and I didnt think to maintain a > > > pristine copy of jslib before making the changes, so I dont have > > > diffs. :/ > > > > > > I am also attaching the sample Python server/client with this email. > > > > > > Meanwhile, i will give the testing one more go, just to make sure it > > > actually does work. > > > > > > Could you also verify it works with your example ? > > > > > > Regards > > > Rajeev J Sebastian > > > > > > > > > > > > > > > On Dec 2, 2007 10:10 AM, Nick P < nick.pend at gmail.com> wrote: > > > > Thanks for the confirmation Rajeev. > > > > > > > > Pete (or anyone in the know here) - I don't know if you have time to > look > > > > at this -- if you don't, but you could tell me some functions to start > > > > looking in in the library itself, I'll take a look. I know very > little > > > > about XPCOM but I might be able to turn something up. > > > > > > > > If I can clarify better let me know - in short, after a server sends > data to > > > > a XUL/JS client, it closes a socket. Instead of the JSLib client > still > > > > being able to read the data that was sent to its socket, it sees zero > bytes. > > > > Expected behavior should be (I believe) that it can still read the > data that > > > > was made available to it. > > > > > > > > Thanks, > > > > Nick > > > > > > > > > > > > > > > > On Dec 1, 2007 11:51 AM, Rajeev J Sebastian > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Hello Nick, > > > > > > > > > > > > > > > On Dec 1, 2007 4:33 AM, Nick P wrote: > > > > > > I am still attempting to use JSLib as a client for a server. > After the > > > > > > server sends a reply message, it closes the socket. Up until the > socket > > > > is > > > > > > closed by the server, the XUL client recognizes that there is data > > > > > > available. When I built a sample client in VB.net, I was able to > read > > > > the > > > > > > available data even after the server closed the socket. However, > with > > > > the > > > > > > JSLib sockets, I have been unable to get it to read the data after > the > > > > > > server closes the socket. > > > > > > > > > > > > > > > > > Am I wrong that this data should still be available for reading, > or is > > > > this > > > > > > unexpected behavior? > > > > > > > > > > I ran the equivalent with Python, and I can reproduce the above > behaviour. > > > > > > > > > > I used a Python based socket server and client.(based on > > > > > http://docs.python.org/lib/socket-example.html, only the server > closes > > > > > the client after receving three times) > > > > > > > > > > With (unmodified) socket.xul , it just gives a message that the > socket > > > > > was closed. However, with the Python client, it returns the data. > > > > > > > > > > I havent done any extensive testing or anythign ... just a 15 minute > job. > > > > > > > > > > Regards > > > > > Rajeev J Sebastian > > > > > _______________________________________________ > > > > > Jslib mailing list > > > > > Jslib at mozdev.org > > > > > https://www.mozdev.org/mailman/listinfo/jslib > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Jslib mailing list > > > > Jslib at mozdev.org > > > > https://www.mozdev.org/mailman/listinfo/jslib > > > > > > > > > > > > > > _______________________________________________ > > > Jslib mailing list > > > Jslib at mozdev.org > > > https://www.mozdev.org/mailman/listinfo/jslib > > > > > > > > > > > > > _______________________________________________ > Jslib mailing list > Jslib at mozdev.org > https://www.mozdev.org/mailman/listinfo/jslib > > From pete at mozdevgroup.com Mon Dec 3 15:43:15 2007 From: pete at mozdevgroup.com (Pete Collins) Date: Mon, 03 Dec 2007 16:43:15 -0700 Subject: [Jslib] Reading available data on recently closed sockets In-Reply-To: <79a035420712031435u2a9bbd48vf5459b610b857e62@mail.gmail.com> References: <79a035420712010851g34e99da8i5171685aa4b474cd@mail.gmail.com> <79a035420712021012w404d6530j904dda0c09b8d10b@mail.gmail.com> <79a035420712031435u2a9bbd48vf5459b610b857e62@mail.gmail.com> Message-ID: <47549493.7030109@mozdevgroup.com> Rajeev J Sebastian wrote: >Hello Pete, > >Is it possible to have mercurial access to the jslib repository in >some standard way ? > >Does jslib still use CVS ? > You can checkout using guest privileges ... cvs -d :pserver:guest at mozdev.org:/cvs login cvs -d :pserver:guest at mozdev.org:/cvs co jslib for any patches please attach to a bug and assign to me for review. and just bug me until I review it. Thanks --pete -- Pete Collins - Founder, Mozdev Group Inc. www.mozdevgroup.com Mozilla Software Development Solutions tel: 1-719-302-5811 fax: 1-719-302-5813 From nick.pend at gmail.com Tue Dec 4 08:26:34 2007 From: nick.pend at gmail.com (Nick P) Date: Tue, 4 Dec 2007 11:26:34 -0500 Subject: [Jslib] JSLib intermittently does not work in Firefox - reinstall fixes In-Reply-To: <4754771B.2010305@mozdevgroup.com> References: <4754771B.2010305@mozdevgroup.com> Message-ID: Pete, No, this doesn't appear to be the case - C:\Documents and Settings\%myname%\Application Data\Mozilla\Firefox\Profiles\0ko2cemk.default\chrome doesn't have any of the jslib files. actually, I just experienced the same thing on my Mac 10.3.9 and FF 2.0 - my chrome files aren't loading now, but they were previously. Again, the user profile doesn't seem to have any JSLib content - just in the FF package itself. I have not yet re-installed to see if this returns it to normal. nick On Dec 3, 2007 4:37 PM, Pete Collins wrote: > Is it possible you have two jslib's installed? > > One in global chrome c:\Program Files\Firefox\chrome\jslib > > and one in your user profile dir? > > --pete > > Nick P wrote: > > > This happened to me once, and I wrote it off as a fluke, but now it > > happened again and I want to ask if anyone else has seen this behavior > > before. > > > > I installed JSLib, and used it successfully. Some time later, I > > loaded Firefox and none of my JSLib .xul examples would load. > > jslib:about and other commands did not work - but jslib:docs did take > > me to the on-line documentation. Restarting Firefox did not fix the > > problem, and I believe I even rebooted and it did not fix the > > problem. Each time I re-installed JSLib, rebooted, and it worked. > > > > Let me know if you can explain this behavior or if you can recommend > > me to look for anything the next time it happens. > > > > Windows XP/ Firefox 2.0, using * *jslib_current_static.xpi* > > < > http://downloads.mozdev.org/jslib/xpi/signed/jslib_current_static_signed.xpi > > > > . > > > > Thanks, > > Nick > > * > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >Jslib mailing list > >Jslib at mozdev.org > >https://www.mozdev.org/mailman/listinfo/jslib > > > > > > -- > Pete Collins - Founder, Mozdev Group Inc. > www.mozdevgroup.com > Mozilla Software Development Solutions > tel: 1-719-302-5811 > fax: 1-719-302-5813 > > _______________________________________________ > Jslib mailing list > Jslib at mozdev.org > https://www.mozdev.org/mailman/listinfo/jslib > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.mozdev.org/pipermail/jslib/attachments/20071204/8e2e8318/attachment.html