This is an inherent problem with the current push protocol. To summarize imagine the following scenario:

a clientside application (GWT or pure JS) initializes and creates a push id. A group and callback are added to this id and a long poll is started. This poll will last X seconds (for simplicity lets assume 50s).

Now, 5 seconds later a new push id is needed with a new group and callback. The listen.icepush call is still outstanding (45 seconds to go) and it has already provided a list of push ids as post data. Thus the client will not receive any push updates to the newly created push id for another 45 seconds (when the next poll is started and the push id is listed in the post data of the next request.).

Not sure what the best solution to this problem is- two come to mind:

1.) kill the oustanding request if a new push id is registered to a callback

2.) update the protocol to not require the push ids as post data in the listen.icepush call.