Re: [Mod-pubsub-developer] Re: Quick question...

[<mod...@li...>]

Uh... this email wasn't signed, but I think it's Dierken?  If so, hi Mike!

Just to clarify, the Mod-pubsub SERVER API has not changed at all yet, except
for one tiny thing that was necessary for the Flash client but should not
impact anything else.  The JavaScript API is the thing that changed
significantly.  JP


--- mod...@li... wrote:

> There is an sourceforge project called 'destiny' that is an HTTP bridge to
> JMS.
> You could use that as a starting point to implement that same HTTP API used
> by mod-pubsub. There's nothing magic about the server implementation of
> mod-pubsub, it's all in the protocol. If mod-pubsub had a multi-server
> protocol for a constellation of messaging servers, that would be more work
> to 'port', but still doable.
> 
> The java client I built is on the old mod-pubsub API, I don't think it's
> compatible with the new server implementation.
> There are actually two java client libraries in CVS for mod-pubsub. One has
> lots of unit tests. Mine doesn't... but still works.
> 
> Let me know if you need advice or additional work for a java client or java
> server - i'd love to help implement a java server.
> 
> I'd also like to implement an RSS format for 'change-lists' (lists of recent
> events) that use 'next' and 'prev' links to traverse past and future
> history - I think that's the correct approach for a REST based event
> notification system.