Running StockListDemo_Basic from file://

[deleted]

Hi,

I need to get the following example up and running locally (i.e. from 'file://' rather than 'lightstreamer.com':

http://www.lightstreamer.com/demo/StockListDemo_Basic/

When I set the domain/context to "" or null as was recommended here before, it doesn't work. I'm using Firefox 4, and am just loading the main html page and misc.js file from the local filesystem - everything else is coming across the web.

pushPage.context.setDomain(null);

or

pushPage.context.setDomain("");

What else do I need to change, please? I would rather run this from file:// rather than on a local Apache server.

Thanks.

Mone

hi,

running from file:/// is not possible. Why do you have such requirement?

see also this thread: http://www.lightstreamer.com/vb/showthread.php?t=903

[deleted]

@Mone, Wrote: hi,

running from file:/// is not possible. Why do you have such requirement?

see also this thread: http://www.lightstreamer.com/vb/showthread.php?t=903

Thanks for the reply.

Is this a browser restriction or a Lightstreamer client restriction? In a secure test environment, If I add netscape.security.privilegemanager.enableprivilege calls to methods that are throwing errors, I can run anything from file:///, can't I?

For various reasons, I can't host the StockListDemo_Basic on a local Apache implementation, so want to test the client directly from file:///. What do I need to change in the lscommons.js, lspushpage.js, lsengine.js and lsmisc.js files to make this run?

Regards.

Mone

Hi,

the issue is related to the same origin policy implemented by browsers;

actually we never tried
netscape.security.PrivilegeManager.enablePrivilege("UniversalBrowserRead") so I'm not sure if that would work; at least out of the box. I may guess that you need that setting on both your html file and our lsengine.html but I didn't try it.

I think that's probably easier and quicker to install a web server and configure the hosts file than try to make that work.

HTH

[deleted]

Using netscape.security.privilegemanager.enableprivilege will circumvent the cross-domain policy (NOTE: be aware what this actually opens up!).

I may guess that you need that setting on both your html file and our lsengine.html but I didn't try it.

Mone

Are all the GETs/PUTs to the www.lightstreamer.comdomain and push.lightstreamer.com domain done from the lsengine.html page?

actually, not.
most requests are made from ajax_frame.html (that comes from the pushserver).
If needed the client falls back using lsform.html . As the environment (ie the app loaded from file:///) is unexpected from our point of view I can't exclude that such fallback may happen in your case.

Alternatively, if I edit the hosts file, should I ONLY add www.lightstreamer.comand not push.lightstreamer.com so that the assets from the www.lightstreamer.com domain will be picked up from the www folder, but that requests to push.lightstreamer.com will go out to the remote server?

yes that's correct if you're going to use our online server and your local webserver.