Jinno
06-05-2008, 10:42 PM
Alright... I apologize for having to do this with such a winded explanation as to what I'm attempting to do, but alas I find it hard to make sense of so many parts of how I would have to implement this. So here's my situation:
Here at my job, we use a Barracuda Networks Jabber Server as our means of in office communication, and public protocol transport communication. We love the security that Jabber brings to the situation.
So enter about a month ago, my boss brings up the fact that the company would like to do a sort of Live-Chat system on our website, and have it work with the current Jabber service. Sounded okay to me, we discussed briefly the basic concept of how it would be done, sketched out some basic plans, did some research, etc. But I had another project or two to finish at the time, so I've just now gotten to the point where I can really sit down and try to work on this.
Well, I went back to the way I was looking at doing it, and realized that I had assumed direct connection of the user to our server through the chat page. Well, my System Administrator (who is much more security fascist than my boss) looked at how I wanted to do it and went "Nope."
So what he suggested was simply having a program running on the server that would manage guest accounts attached to the Jabber server. The web-program would initiate a call to this client, which would maintain a pool of like 3 users, and place the others in a pool to be connected later. A connected user would be talking to either one of our Sales Representatives or one of our Recruiters, and the program would manage input from the user and communicate it to the Jabber server, and would manage Jabber Server input and then communicate it to the user.
That is in a nutshell what I'd like to try to do. I know that the members of this forum likely know the protocol much better than me and have probably seen some form like this in their own experiences with Jabber Development. Our Servers are Windows-based and we use ASP.NET C# for our web development.
Thank you in advance for your help,
~Brandon Jones
Here at my job, we use a Barracuda Networks Jabber Server as our means of in office communication, and public protocol transport communication. We love the security that Jabber brings to the situation.
So enter about a month ago, my boss brings up the fact that the company would like to do a sort of Live-Chat system on our website, and have it work with the current Jabber service. Sounded okay to me, we discussed briefly the basic concept of how it would be done, sketched out some basic plans, did some research, etc. But I had another project or two to finish at the time, so I've just now gotten to the point where I can really sit down and try to work on this.
Well, I went back to the way I was looking at doing it, and realized that I had assumed direct connection of the user to our server through the chat page. Well, my System Administrator (who is much more security fascist than my boss) looked at how I wanted to do it and went "Nope."
So what he suggested was simply having a program running on the server that would manage guest accounts attached to the Jabber server. The web-program would initiate a call to this client, which would maintain a pool of like 3 users, and place the others in a pool to be connected later. A connected user would be talking to either one of our Sales Representatives or one of our Recruiters, and the program would manage input from the user and communicate it to the Jabber server, and would manage Jabber Server input and then communicate it to the user.
That is in a nutshell what I'd like to try to do. I know that the members of this forum likely know the protocol much better than me and have probably seen some form like this in their own experiences with Jabber Development. Our Servers are Windows-based and we use ASP.NET C# for our web development.
Thank you in advance for your help,
~Brandon Jones