Matthias Sachs commented on Jul 16, 2013

How to keep the general sametime status?

In your article you write "You must perform a login on every page" and you use the loginByToken function to do that: "stproxy.login.loginByToken("A.N.Other", stproxy.awareness.AVAILABLE,". Unfortunately you have to submit the initialStatus with this function, so if you've done a login in an other page before and changed your status there (i.e. to AWAY) the status will be resetted to AVAILABLE on all pages. Do you have an idea how to handle this problem?

Brendan P Murray commented on Apr 24, 2013

Re: Integrating IBM Sametime in a Web application without the Dojo Toolkit

You're making a very common error: localhost is not a real address, so the cross-domain functions cannot work. To make this work, you MUST use a fully-qualified domain that is listed in the Sametime Proxy's list of permitted domains. While this can be awkward when testing, you can work around it by creating an alias in your hosts file for one of the permitted domains. Alternatively install a lightweight server on your local PC, such as lighttpd, and serve up your test page from that.

Brendan Murray commented on Feb 15, 2013

Re: Integrating IBM Sametime in a Web application without the Dojo Toolkit

You cannot use localhost because of the underlying mechanisms to handle the JavaScript same-origin policies. If you want to test this, you need a proxy server that is addressable, e.g. www.ivo.com, and the application server which can be on the same domain, but it *must* have a URL of the usual form, no abbreviations, no IP address, no "localhost".

If you're running a local server, simply add the test address to your hosts file and spoof this to allow it to work. That way you can provide an acceptable address, while still running locally.

Ivo S Rahov commented on Feb 8, 2013

Not able to establish a full connection

Thanks for the article!

The problem that I face is that I cannot establish a full connection. I get the following error:

"Not connected to by an allowed domain. (http://localhost) "

so "stproxy.onLoad(MYFUNCTION)" is never called

After some debugging I saw it comes from hubClient.jsp where there is some configuration for "domainList" which in my case is false, thus falling back to using the URL of the stproxy.

I suspect that that there should be some server side configuration for those allowed cross javascript domains which will populate that list (in my case I should be able to allow 'localhost').

So I'm not able to run neither your example, nor the examples included in the official documentation.

Any help will be much appreciated.