Agent == Smith

Group Project Page - Chat Server

Recent News:

May 02, 2005 -- FINAL

We have made MAJOR progress on our chatServer. We are still fighting a few bugs, but at this point it looks like they may be with us when we turn the project in tomorrow morning. The major breakthrough of the day is that we have a working chat client which will demonstrate all of the functionality of our server.

Agent==Smith chat client GUI

All of the documents have been written, we are working on final testing and debugging as we speak.

In other major news of the day, we were pleased to add Atlas, and AgentICE, and InternationalFIPA Hacks to the groups that we have achieved full integration with. We are still working with DACK, and Licking River hoping that we can pull something off tonight. Things with J.I.H.A.D and Spanky's Ninjas are still awesome!

It has been a long haul, but thankfully we can see (and almost feel -- but for the windowless lab) the light at the end of the tunnel.

April 29, 2005

ChatServer Goes Beta!

Lots of great things have been happening in the last couple of days. We have been working to implement our wow features, along with putting the ChatServer through a lot of tests. We want to make sure that we supply a piece of software that is robust and easy to use. As a team, we feel like we are really making a lot of good progress, so with tonight's build we would like to announce that we have gone into beta.

We have spent some time in the lab with Spanky's Ninjas and J.I.H.A.D. over the past couple of days, and are very pleased to announce that we have been able to integrate our agents!

Agent==Smith chat server hard at work
The chat server its self isn't the most beautiful thing, but it works!

J.I.H.A.D. player agent doing its thing
J.I.H.A.D. has a clean player agent GUI that is fully integrated with the Spanky's Ninjas game server and the Agent==Smith chat server!

There is a lot more to say and update with regard to our wow features, we should have those expansions and explanations posted here on our website by the end of the weekend. Our team is currently working hard to create our own stand alone chat client for the purpose of showing off the full functionality of our chat server.

We are aware that there are still some teams out there that are interested in integrating with us, we should be around and about on campus for the next few days. Please don't hesitate to contact us in order that we could set up a time to integrate and test with you!

April 28, 2005

It seems that there is a bit of confusion about who is responsible to actually create/maintain chat rooms. In effort to try and clarify, we have created a flow document for you to take a look at. This is how we are expecting things to work. If this is different than you had expected, please let us know ASAP. We would like to try and get demos and tests taken care of before the end of the week.

April 26, 2005

We are into our last leg of the development on our ChatServer. Today we decided on the final "wow" features that we would add, and they should be completely implemented by Friday.

We sent out emails to the groups that had expressed interest in collaborating with us, requesting a time to set up an integration meeting with them ASAP.

April 25, 2005

It was a productive weekend for Agent==Smith. We managed to get our Alpha server debugged and running smoothly. We also made some great progress on adding more functionality to the server. We have added a config file that helps with the setup of the server, and have added an optional content filter. This week we plan on adding a few more features, but more importantly we would like to make sure that we are integrating well with the other teams, and that we have made progress "administrative" stuff outlined in part D of the project.

April 21, 2005

Follwing the example of SEED, we also have decided that having a DLL that would formulate XML strings that conform to our specification would be usefull to our collaborators. So without further ado we announce ChatMessageBuilder, Download verion 1.0 today. As it is new, if you experience any problems don't hesitate to shoot us a message.

If you would like to read about the DLL before you download it, check out the "read me".

We are still busy testing and working on making our agent solid and reliable. The basic specification is now completely implemented, and we are beginning to work on server reliability, and "WoW" features.

April 19, 2005 -- 11:30 pm

Update!!

IT'S ALIVE! Yes folks, we have an ALPHA version up and running. We can send and receive messages on a local machine, and on a closed direct ethernet connection! We are of course going to have to do some more serious testing in the few next days, but it looks like we are about ready to begin on the wow features! Special thanks to Spanky's Ninjas for allowing us to use their webServer for remote testing!

April 19, 2005

We think that things are back on track now. If you check the link at the right for our message spec, you will see that we have made some significant changes to the way that our message structure works. We have discussed these changes with our collaborative groups, and they seem to be pleased with the change. If you are still having problems with this updated spec PLEASE send us a message ASAP.

Things with our chat server are really coming along, and we should have an Alpha version of the chat server to share with the world soon. We are beginning to think about "wow" features, and if you have any suggestions, we would love to hear them.

April 16, 2005

OOPS! It seems that there is a small problem in the way that we designed our XML messages. Our group decided that rather than fighting with MSXML we would just parse/create our XML by hand. Which means that when we designed our messages, they were formed in poorly structured XML.

In hope of fixing this problem, we would like to propose the following change. At the front of each message tag in our spec we would add "cs" short for chat-server, but more importantly, it will create an appropriate XML node by the name of "cs". All of the attributes would remain the same.

A sample tag would look like this:
<cs instr="chat" msg="room already created" html="room already created(with html tags)"/>

We would like to leave this open as a proposal for the rest of the weekend, if we don't hear of any negative feedback by Monday we will change our spec to reflect this addition.

April 14, 2005

Today we had a meeting and made programming assignments. The project is really taking off now. We have formed an aggressive programming schedule, and hope to have working code ready for initial testing early next week. If you are following our development, we would really appreciate it if you could take a look at our message specification, and make sure that it will do what you expect it to. We are getting close to the point where making spec changes won't be as convenient or easy as it was in the planning stages.

If you are interested in implementing our chat server, and would like more information, don't hesitate to contact us!

April 13, 2005

Things are really beginning to move along and come together. There has been a lot of communication with various groups that are interested in integrating with our chat server, and we are glad for the business. After several days of designing and planning, we are ready to begin the coding phase of the project.

For those that are interested, here is our message specification.

April 8, 2005

We had a good team meeting today. It was a chance to meet, throw out some preliminary plans, and firm up some other plans that we allready had on the table. One of the most important decisions that we made today has to do with how our customers will use our chat server. Because everyone is in the development process, we thought that we would publish them here for your consideration.

  • Messages to and from the chat server will use the same content field as the ACLMessages in homework 7.
  • The content field should look like this:
    • <instr="chat" msg="your text message" html="your text message with html tags"/>
  • The following "instr" attribues will be recognized: (More on the specific args that go along with them to come later.)
    • chat
    • createroom
    • removeroom - (owner only)
    • addplayer
    • removeplayer
  • The CONVERSATION ID in ACLMessage is the number of the chat room (assigned by the server), this is what routes your chat message to the proper chat room.

We understand that this is a rough first shot, but it is enough to let some of you early adopters know what we are thinking about.

April 5, 2005

We were very pleased to learn that our team was approved to build a chat agent, which was our first choice! We will post more about our interface as soon as we have it designed. Check back soon for more deatils.

April 4, 2005

We have met for our first formal team meeting, and things are looking really good. We were able to formalize our job funtions, and decide on which type of agent we would prefer to build.

April 3, 2005

The site has been created with its public/private sections, and has links from which the whole team or individual members can be mailed. More soon to come!