[Jslib] Changes to socket library

Pete Collins pete at mozdevgroup.com
Thu Feb 17 13:14:14 EST 2005



Richard Morris wrote:

> I have been using the JSlib sockets module quite extensively for the 
> past year. Just recently I tested with JSLib *0.1.248, and I noticed 
> that the socket functions had changed, and none of my applications 
> would connect via sockets anymore. AFAIK, the visible changes are 
> fairly simple, as I can see from the changelog in socket.js, but even 
> after a rewrite I still seem to get only sporadic results with both 
> Mozilla and Firefox. Sometimes I will connect, and then will get the 
> error "Socket.read: not connected" for no apparent reason the next 
> second. Other times, I cannot write to the socket, even using the 
> standard sockets.xul sample from JSLib.


stknight recently re-factored the socket code ...

A regression perhaps?

>
> Has anyone else noticed problems with the latest version of JSLib 
> sockets, or is it more likely that I am missing something?
>
> By the way, I also cannot get jslib.init(this) to work with Firefox 
> 1.0 or Mozilla, again from the JSLib samples. I get the error "jslib 
> is not defined". (Solved for now by loading JSLib the old way.)

I would need to know more information. What jsLib package?

In what context are you calling init - from a chrome url?

--pete

-- 
Pete Collins - Founder, Mozdev Group Inc.
www.mozdevgroup.com
Mozilla Software Development Solutions 




More information about the Jslib mailing list