Hi all,
it's interesting to see that the same ideas are born all over the world
:-) The link bellow shows the fragment of GDML processing architecture which
has been designed with the publisher/subscriber in mind. It's in C++ and
virtually for any XML document but to extend it for the HTTP and network
wouldn't be a problem. I have implemented it this summer in july :-) I plan to
release it as an open source project soon.
Look at it at: http://cern.ch/gdml/chep01/node10.html
Cheers
Radovan
> Dear XUpdate and XSmiles people,
>
> We have been experimenting with XUpdate in what we believe is a
> novel way, and
> one which we think would make XUpdate attractive to a much wider audience.
>
> We use it at the client end to modify a Browser's DOM with updates
> "pushed" from
> a data source. In our experiments, the data we update is a real
> time graph in
> SVG format. We have used the XSmiles and Internet Explorer
> browsers. (In both
> cases using the Csiro SVG rendering engine, JMS to deliver the updates, and
> Lexus to apply them).
>
> We work in an industry where publish subscribe of real time
> information is very
> important (price information from exchanges). There are a number of
> commercial
> products in the market place that supply publish subscribe
> infrastructure. We
> are convinced there is a latent demand for this sort of capability in other
> industries as well as our own. Our experiments combining Csiro,
> Lexus, XUpdate,
> SVG, XSmiles and a publish subscribe protocol handler using JMS have
> demonstrated that this latent demand could be satisfied more openly.
>
> We address this note to both the XUpdate and XSmiles teams first to
> thank you
> for the excellent technology that you have given us, and second to
> highlight the
> potential synergy of the combination.
>
> We have a few issues and questions:
>
> 1. We would like to see the idea of using XUpdate in conjunction with a
> publish/subscribe browser environment promoted more widely. Do you
> think this is
> feasible, and can you offer any suggestions about how best to achieve this.
>
> 2. As far as we can see, XUpdate is not yet part of the W3C family.
> This may be
> because it has been perceived as an esoteric issue for XML
> databases only. Do
> you
> think that exposing it as a client side technology would add enough
> interest to
> the extent that it could be submitted to W3C. Certainly we have a
> concern that
> it could become a defunct technology if it stays outside W3C, and
> this concern
> was re-inforced by the recent request for developers sent out on the XUpdate
> mailing list.
>
> 3. The publish subscribe protocol will need to be standardised. It clearly
> differs from http: in that updates arrive after the initial page
> value. Neither
> is it like the current streaming media protocols which handle real
> time data of
> a quite different sort. There has been much talk of "push"
> technology, and yet
> as far as I know, no such protocol has yet emerged. Apart from the
> commercial
> products mentioned above, so called "push" technology has really
> been based on
> hidden "pull". Perhaps the Xsmiles team could comment on the feasability of
> introducing such a new protocol (pshttp:?).
>
> Your comments and suggestions about how to move forward would be welcome.
>
> Regards Gordon Jones and Finnian Reilly
> --
> ______________________________________________________________________
> Lars Martin mailto:[EMAIL PROTECTED]
> SMB GmbH http://www.smb-tec.com
>
> ----------------------------------------------------------------------
> Post a message: mailto:[EMAIL PROTECTED]
> Unsubscribe:
> mailto:[EMAIL PROTECTED]
> Contact administrator: mailto:[EMAIL PROTECTED]
> Read archived messages: http://archive.xmldb.org/
> ----------------------------------------------------------------------
>
----------------------------------------------------------------------
Post a message: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Contact administrator: mailto:[EMAIL PROTECTED]
Read archived messages: http://archive.xmldb.org/
----------------------------------------------------------------------
