Hi! On Wed, Aug 5, 2009 at 11:35, Bernd Fondermann<[email protected]> wrote: > As the GSoC'09 is nearing 'pencils down' state, I'm thinking about how > to showcase PubSub in an easy way. New features are not critical, AFAIAC.
Thanks! I was just plotting how to integrate the various access-models which seems more tricky than I thought. Maybe we'll need to discuss them at a given time. > My proposal is to implement a simple Swing application, featuring: > + a simple UI, with the following forms: > a. JID edit field (EF), hostname EF, password EF, "login" button > b. Node name EF, "subscribe" button, "unsubscribe" button > c. Text area, "publish-to-node" button > d. Text area for displaying messages > + Use case: Login > User specifies JID + password, when hitting login, the user get's > logged into the server given by hostname > + Use case: Subscribe to a node > User enters node name and hits subscribe. > Client creates the node, if not already existing. > Client sends subscription request. > Server subscribes JID to the node > + Use case: Unsubscribe from node > ... canonical ... > + Use case: Publish > User enters a message (not whole stanza) into the text area, > hits "publish..." > Client publishes the message to the node on the server > + Use case: Receive pubsub messages > Client displays messages coming from the server in the display area > > WDYT? Showing a real world example would do more good (and is in line with our GSoC proposal) than implementing more features of the spec. Even though I've got more experience with webapps than any other UI technology, they would not be able to show the advantages of the pubsub approach. I'll start right now, building on top of my previous example. Where should I put the code? Michael
