From: Joyce P. <tru...@ya...> - 2004-10-17 21:22:03
|
Forwarding for Alex: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 17 October 2004 12:59 pm, Asynch Messaging wrote: > > [...] our new JavaScript client would require changes to all the > > old CGI apps > > What are the nature of the changes? Minor replace of 'kn' with > something else, or a completely different API set? So I think I can answer that one (since I'm the guy that wrote the new client library). The client included in repubsub.tar.gz library is a rewrite from top to bottom. It no longer supports 4.x browsers in any way, but now provides support for Safari and doesn't do the whole "stop everything, re-hoist, now GO" dance any more. All of the interfaces for using the library are likewise different, since the dispatching method used internally is based on Signals and Slots instead of context piclking. This also makes the client an order of magnitude faster than the old one, and something like 1/3rd the size. Internally, the library now supports both "peering" and "non-peering" modes, where the default is now "non-peering", which makes for a much more robust client. The API for subscribing and un-subscribing is completely different (and hopefully easier to use), although I do recognize that the APIs for this are getting lost in the noise of the documentation. I plan on adding a facade API that will give us the simplest way to perform the common actions needed in writing for pubsub. Until then, the RSS scroller demo should give you a feeling for how to use the new API. The docs for the new client are avaialable at: http://mod-pubsub.org/repubsub/docs/repubsub.html or: http://mod-pubsub.org/repubsub/docs/repubsub.pdf Regards - -- Alex Russell al...@do... al...@ne... F687 1964 1EF6 453E 9BD0 5148 A15D 1D43 AB92 9A46 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFBctVBoV0dQ6uSmkYRAslvAJ40QMoFmo0/xLS8WQh91LVNtdU7cQCfeSG4 r7+9UbQHdEujWysmfAot13c= =Joze -----END PGP SIGNATURE----- --- Asynch Messaging <asy...@ho...> wrote: > > > [...] our new JavaScript client would require changes to all the old CGI > apps > What are the nature of the changes? Minor replace of 'kn' with something > else, or a completely different API set? |