Well, to answer your question exactly it would be possible with a massive amount of work getting jetspeed/turbine to use server-side push. But I don't think that is feasible or desirable. You can also set a client refresh for x seconds to refresh the page, this is more feasable and could probably even be triggered by the portlet action in question if the data hasn't loaded in x seconds.
We have some code here at Cisco that does two similar things you might be interested in:
1) asynchronous portlet rendering for better performance.
2) timeout associated with portlet data loading so that you can set a threshhold. If the data loading takes more than X seconds, the portal will continue rendering and simply put a error message in place of the getContent for that portlet. I suppose in that case you could also set client refresh in the headers to try again at some specified time.
If there is enough interest I could rework this code to be more general and post the code and documentation here.
%regards -tk
At 10:36 AM 10/28/2003 +0200, Youssef Mohammed wrote:
buildNormalContext sends the HTTP Response to the client ( e.g. the browser ) and It is called when by an HTTP Request by the client . So how can you do this Server Side ?!! You can't push your data to the client !!
The work around for that it to refresh your portlet every X seconds and check for your thread status
-----Original Message----- From: Anuraag Sarangi [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2003 3:17 AM To: Jetspeed Users List Subject: how to call buildNormalContext manually
Hi,
I have a portlet that spawns a thread and waits for notification from a service. After the notification, I want to call the buildNormalContext again from the thread, or refresh the portlet from the thread. How can I do that?!
Thanx in advance, Anuraag
__________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
