On 20 January 2011 02:39, Vicente J. Ruiz Jurado <[email protected]>wrote:
> Thanks Alex, > > El 19/01/11 04:45, Alex North escribió: > > Hi Vicente, > > > > I'm not sure integration by trying to compile the WIAB code in with your > > application is the best approach, but perhaps you can tell us more about > > what you're trying to do so we can judge. > > For instance, we have a xmpp gwt library/client: > https://code.google.com/p/emite/ > that we integrate in other GWT apps (then you can chat while you are > doing other things different that chatting). We want to make a similar > integration with WIAB in another FLOSS project (as a brief-summary). > > With emite, we use a servlet to proxy all the BOSH petitions to the xmpp > server. Can we try to proxy all the WIAB client petitions in a similar way? > Note that Wave uses XMPP only for federation (and even that is under threat). The client-server protocol is not XMPP, it's json messages (derived from protocol buffers) over a websocket. I don't know how feasible it is to proxy a websocket. I'm sure it's possible, I just have no experience. > Maybe some guidelines in a wikipage related to integration will be great > (with so much jars and dependencies it's not straightforward). > > In emite we have an integration sample project to show how to use it > with other GWT projects. To make tests, yesterday I started a GWT sample > project that only integrates and starts WIAB via jar dependencies (and > we use maven). For now, only starts the WebClient... Maybe something > like this can be useful to others. > > We have to facilitate the use of the Wave protocol here and there easily ;) > > > The code under the org.waveprotocol.wave package is intended as re-usable > > library code, and the build file can build it into jars for you to link > > against. The code under org.waveprotocol.box is the WIAB application > itself > > and we never thought about it being compiled or linked into another > > application. Guice is used for some pieces, but not universally because > > Guice doesn't solve all problems. There's no commitment to keep > interfaces > > or bindings remotely stable within that code so I think integrating that > > deep is likely to be painful. > > Yes indeed. For now I have running the WIAB client code (and our code) > against a port and the WIAB server running in a different port. > > > However, you're hinting at something we would like to do, which is to be > > able to delegate WIAB authentication to external authentication systems. > I > > had imagined this would involve a general auth interface in WIAB with > > multiple implementations of that interface, something without too much > > churn. So WIAB would still be a stand-alone binary but you could switch > auth > > systems by configuration. Ditto persistence. > > > > Alex > > Yes, without other alternatives, I was trying to do this via Guice (via > injections, interceptors,...). > > Thanks indeed, > > > Vicente >
