Subj : Re: web services To : netscape.public.mozilla.jseng From : "Mark Turansky" Date : Fri Dec 05 2003 10:42 am I profess ignorance about the WebServiceProxyFactory or other APIs in Mozilla, but I still have my $0.02..... If there is a component responsible for web services, couldn't a simple JavaScript object (extending ScriptableObject) be used to wrap the component, thereby making it available to javascript? I think the Facade pattern would fit here. Make the Facade an easy pass-through to the more complicated web service API. As per the Gang of Four, the Facade to the web service would make the entire subsystem (the web service) easier to use. would that not work? "Johnny Stenback" wrote in message news:3FCFD700.6000306@mozilla.jstenback.com... > Jim Wang wrote: > > Is it possible to take the web service API such as WebServiceProxyFactory in > > Mozilla to be available to server-side JavaScript? How? > > > > Possible? Yeah. Trivial? No. To do that you'd need to pull in all of the > code that the web services code depends on, and that means at least > XPConnect, the JS engine (obviously), XPCOM, parts of the Mozilla DOM > code (mozilla/content and mozilla/dom), xmlectras, necko, expat (and > parts of mozilla/htmlparser) and probably more. On top of that you need > to re-think the async/sync IO model that's used in Mozilla. > > It'd be awesome to have this done and have instructions on how to do it, > so if this is a task you're interested in doing, let us know and I (and > onthers too) can try to advice as much as I can. > > > Thanks > > > > Jim > > > > > > > -- > jst .