I am so close to having this working with the Plumtree Portal.  There is just one little problem that I'm running into.  I have all of the Providers and Adapters built, and they are working great.  And I have my web application built, and it works great.  I can go into the administrative part, and add new lobbies, etc.

Here is my problem:
When I click on a link to a chat room, the chat room comes up, but it cannot connect to the server.  Here is why: we have two servers for our portal - one that is the front end server, that the browsers connect to.  We'll call it portal.company.com.  We also have a backend server that hosts all of our web applications - we'll call it app.company.com.  So when a browser clicks on a link to the chat room, the following page loads:

http://portal.company.com/http%3B/app.company.com/ChatApplication/CuteSoft_Client/CuteChat/CH_MainForm.Aspx?...

This works great.  It loads the following pages using the same path, without any problems:
utility.js.aspx
WrapGecko.js.aspx
ch_style.css
ch_skin.js.aspx
Skins/Normal/Layout.js
Skins/Normal/Style.css
chat.rane.js.aspx
chat.rane.aspx
ch_mainform.js.aspx

So all of the files are loaded properly, including chat.rane.aspx.  So far so good.  Then it tries to do a post to chat.rane.aspx to connect to the chat server, showing "Please Wait, connecting to server" in the browser window.  When it does this POST, it should be posting to the following URL, using the path used for all of the GETs above:
http://portal.company.com/http%3B/app.company.com/ChatApplication/CuteSoft_Client/CuteChat/chat.rane.aspx

However, it is really posting to this URL:
http://portal.company.com/ChatApplication/CuteSoft_Client/CuteChat/chat.rane.aspx


Here is why I think it's doing this:

Whatever is causing Cute Chat to try to connect to the server is using the following to define where chat.rane.aspx is:
"/ChatApplication/CuteSoft_Client/CuteChat/chat.rane.aspx"
This does a relative URL, relative to the server name.  What should be done is a relative URL, relative to the current directory, such as this:
"chat.rane.aspx"
That way the browser will do a post to this URL, which will work:
http://portal.company.com/http%3B/app.company.com/ChatApplication/CuteSoft_Client/CuteChat/chat.rane.aspx


If we can get past this, I think we will have this working for the Plumtree Portal.

Thanks for your help,

    Tim Larson

Tim,

---

asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
asp wysiwyg html editor: http://cutesoft.net/ASP
asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
Live Support: http://cutesoft.net/live-support/default.aspx

Yes, the site is online, and I have an account and password set up for you, but I'm not sure what the PM is. 

Thanks,

   Tim Larson

---

asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
asp wysiwyg html editor: http://cutesoft.net/ASP
asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
Live Support: http://cutesoft.net/live-support/default.aspx

I figured out a way to get a temporary workaround.  I opened up the CuteSoft_Client\CUteChat\chat.rane.aspx file, and changed the ProcessRequest function.  Here is the old version:


And here is the new version:


What I effectively did was to reassign the ChatRaneService variable to have just "chat.rane.aspx" as the URL, rather than "/ChatApplication/CuteSoft_Client/CuteChat/chat.rane.aspx", and this seems to fix the problem.

Ideally, CuteSoft.Chat.Rane.RaneHandlerFactory.ProcessRequest should be modified.

Please let me know what you come up with.

Thanks!

    Tim Larson