Well, in the AJAX world, you would write a JavaScript that sends an XmlHttpRequest every couple of seconds, and modifies the existing web page. But we're in a revCentered world here, so let's take the other route :-) Along the same lines, you could make a revlet that uses 'get url' and 'post to url' commands in a 'send in time' loop to interact with the server back-end, and update the user interface with the changes. If your server back-end can send the information in XML or JSON format, you can still decide later on to make an AJAX-style front-end.
Pushing information from the server to the client is more complicated, and requires some form of socket communication. My favourite solution for this problem is putting a message queue (like Apache ActiveMQ) in between the server and clients. At the RunRevLive conference, I did a presentation 'revTalk meets Java' where I showed this method in two ways: by calling a small Java class via shell call, or by using the Quartam STOMP Library, a 100% revTalk solution to talk to Java JMS-compatible message queues. Quartam STOMP library will come out as soon as I find the time to do another debugging round and finish the documentation. It will be open source, dual-license LGPL / Commercial. Jan Schenkel. ===== Quartam Reports & PDF Library for Revolution <http://www.quartam.com> ===== "As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld) --- On Tue, 11/17/09, Bill Vlahos <bvla...@mac.com> wrote: > From: Bill Vlahos <bvla...@mac.com> > Subject: Online status board > To: "How to use Revolution" <use-revolution@lists.runrev.com> > Date: Tuesday, November 17, 2009, 4:20 PM > I would like to make a application > using the new capabilities in Rev 4 that I am having trouble > figuring out. It is for checking out resources so people can > see who has the resources checked out. > > For example: > Room A * In O Out Fred Smith > (these would be radio buttons followed by the name of the > person who checked it out) > Room B O In * Out Available > etc. > > I'd like the clients to be able to see the status in a web > browser. The checking in and out would be set in a server > application which people log into. The client web browser > would need to be able refresh itself. A screen refresh would > work except it is ugly (whole screen clears and redraws) and > it wouldn't by dynamic. I'd like to be able to push the > updates to it in real time. > > It seems like this is a good candidate for the plugin to > make the updates smooth but it could also be done using Rev > like a PHP server. > > I can see how to save an application in Rev 4 for the > plugin but I don't see how it would read the changes and > update the client. This could also probably be done in Rev > like PHP so it is just updating HTML but I'm not sure how to > get started there. > > Any ideas on how to start this? > > Thanks, > Bill Vlahos > _________________ > InfoWallet (http://www.infowallet.com). Remember the > important details of my life. > > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage > your subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution