Portlets can be as simple or as complex as you want. It depends on who is notifying who and whether or not you need to safe state.
For something like this I would create a Turbine/Fulcrum service that the portlet could check on a routine basis to determine the state of the EJB r, Hugh ----- Original Message ----- From: "Richard Greenane" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, July 27, 2002 5:32 PM Subject: Can jetspeed be used for real time apps? > Hi there, > > I understand that technically portlets should just be simple bits of > media and aren't particularly interactive but I would like to have a > portal that does different things depending on what is happening in an > EJB back end. > Is this possible? > > I have read a couple of suggestions that a socket could be opened and my > back end events could then contact the portlet. However someone else > suggested that jetspeed portlets do not stay *live* for very long and > the socket would close. Does anyone have any suggestions on another way > to get real-time events from a back end server to a portlet? > > Many Thanks in advance > > Richard > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
