Re: Any plans for...
Aleksander Slominski <[email protected]> Sat, 19 Nov 2005 14:42:17 -0500
| Newsgroups | gmane.comp.apache.webservices.wsif.user |
|---|---|
| Message-ID | <[email protected]> |
Andrzej Jan Taramina wrote: >Alek: > > > >>key client side abstractions i have prorotyped are XService (that >>represents a local objects that provides access to a service described >>in a WSDL): >> >> > >I'm thinking that there would be value in keeping the client and server side >stuff separate. Or at least modular enough that you can pick/choose which >you want. > > it is completely separate (or as separate as you want - still you can expose service on local machine, the same JVM etc) with some extra work to host (local Java, BeanShell, whatnot) or bridge to existing services (like EJB). >I expect more folks will want the WSIF-style client invocation API rather >than the server side service implementation stuff. Primarily because there >are already a lot of toolkits that generate the latter. > > true but you need minimal server side to do true asynchronous invocation as in such situation you are doing peer-2-peer computing not client-server (every client is at least on logical level also a server - sai that you can use intermediaries such as WS-MsgBox service to allow client that can not have listening socket - ex. applet - to pull messages ...) > > >>think about it as a *prototype* for next-gen WSIF - if there is >>something useful then it may be used (or improved) in the next WSIF >> >> > >Ah! Now I understand. Excellent! > > ;-) > > >>direction and everything else depends on users and where they want to >>take it ... it is that simple and WSIF definitely needs more active >>developers :) >> >> > >+1 on that. > >No decisions yet, and given how close the Xmas season is, I might not make a >decision till after the holidays. > >But I am tempted by the thought of extending the inventory of WSIF providers >to include REST/HTTP (I believe Oracle has this already...sad that they >haven't donated it back to the WSIF project), ebXML Message Service and also >updates to be able to handle the impending WSDL 2.0 spec. > > > cool! alek -- The best way to predict the future is to invent it - Alan Kay