Skip to Content


Wondering if anybody can give me any ideas as to whether or not this can work in a portal environment.

There is an open source solution for auto-refreshing called pushlets. On the client side, it basically is an HTML page with two frames. One frame is the display and the second frame calls a servlet which subscribes to a certain subject (through a parameter). When a response is returned from the servlet, the response calls a javascript function in the main HTML page to refresh the display frame (or display new data from the servlet response). I've already proven that these pushlets work in a non-portal environment...However, I am having trouble trying to integrate it into a portal environment.

Any ideas???

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Posted on Oct 01, 2003 at 09:47 AM

    Thanks Oliver,

    The idea I came up with was to use two iViews.  One iView acting as the "so-called" display frame. And of course the second iView acting as the frame which calls the servlet. Then in the response from the servlet, I would raise an event using EPCM in javascript. The display iView would be listening for this event and then reload the iView.

    Another problem I am having is that in the pushlet framework, there is a Publisher class.  This class has only one instance running at all times. This Publisher keeps track of the subscribers and also dispatches the events to the correct subscribers. I don't know how I can create this Publisher in the portal framework.

    What do you think Oliver?


    Add comment
    10|10000 characters needed characters exceeded

    • Sorry let me add to the information above.  The Pushlet servlet, after creating a Subscriber instance, waits for a response. And the response is the Publisher dispatching the event in the form of a Javascript call.

      I just wanted to make it clear as possible.