Hi Adam

Code is written just fine to work as a stand alone aplication. The issue comes when using it with the portal. Here is an insight how our portal environment is setup.

We have a portal server and another Application server (portlet server). Portal server hosts the Core portal application. And portlet server hosts all the application that run as individual blocks and are placed in portal pages.

When a client accesses a portal, any request going to application unit residing on portlet server is proxied through the portal server.
URL looks something like this
http://portal.com/portal/proxyapplication/http;//portletserver/cutechat/CH_mainform.aspx

Note there will be two sessions created; 1 on the portal server, 2 from portal to portlet server
As long as the requests are proxied through the portal like http://portal.com/portal/proxyapplication/http;//portletserver/cutechat/anyASPXorHTMLfile things will work good. But any link in code that is relative to root of the portlet application virtual directory like "/cutesoft_client/cutechat/chat.rane.aspx" will result in error. This is because it will look for http://portal.com/portal/cutesoft/cutechat/chat.rane.aspx path which is basically the portal server and NOT portlet sevrer. Fix is to use link path relative to the current location, like "chat.rane.aspx" or using "../../Login.aspx".

I think there are links in SWF source code that are reltive to ROOT of cutesoft application. And this is causing problem on our side. We are intersted in your product and would appreciate if you can help us integrating it in our environment.

Thanks much
Kuljit