Multiple connection warning alerts from Firefox

[Alessandro]

Thank you for the explanation Alex. I was not necessarily looking to circumvent any such restriction, just have control over the text and placement of the error message - in general we consider a popup alert refering to "Lightstreamer" (which the end user may or may not have any knowledge of) is less than friendly. Feeding the error through the normal reporting callbacks already in existence seems preferable - and you can still refuse to start the engine as now.

Waddy, your considerations make sense. We promoted that alert to bypass any customization, to be sure it was not lost, but we'll probable introduce a way to customize the text or block it in a future release (quite soon).

I will go investigate the alternate engine creation strategies you pointed out, I'd only just my code converted to the loadEngineMinimal method, now I notice it is deprecated!

Yep, more clear and rational methods were introduced with Web Client 4.2: createEngine() and seekEngine().

It is not clear to me what all the consequences of supporting sharing an engine across windows are, especially if the original push page that loaded it is closed. It makes sense for frame based apps, but if multiple browser tabs or windows are open - I'm just not sure.

In that case, when the Master Push-Page is closed, all the pages stop pushing. But when a new Master Push-Page is created all the existing pages automatically attach to it. In a future relase of Lightstreamer, the automatic migration of the Master Push-Page will be implemented, that is: if the Master Push-Page is closed, an existing Push-Page is eelcted and becomes the new Master Push-Page automatically.

[Mone]

Hi All,

following Waddy's advices we've added a new callback to both PushPage and LightstreamerEngine objects called onClientAlert.

The new callback differs from the onClientError (1 2) callback in the message's purpose. While onClientError's messages targets the developer to warn him about possible problems, the onClientAlert's messages notify the final user on any critical conditions, related to its environment, that prevent the application from working.

The default implementation shows an alert so that the behavior is kept the same as the previous versions of the web client. To stop the alerts substitute the default callback with an empty function is enough.

Check these links for details:
http://www.lightstreamer.com/docs/cl...#onClientAlert
http://www.lightstreamer.com/docs/cl...#onClientAlert