COMP 310 Fall 2010	Lec31: ChatApp Interfaces...

For reference, be sure to keep in mind the design principles we discussed last time.

Considerations for today:

• IChatRoom -- fully serialized object, not stub   ==> no central server!
• Connection Use Case: The initial connection returns an IConnection stub, whose getChatRoom method returns the currently connected chatroom.
  • What must be true about the target computer before it is connected to?
  • What if the target computer has not connected to anyone else yet?
  • How does this change our initial connection use case? 
• IChatRoom.sendMsg() returns generic ADataPacket or a status type?
• IUser methods
• Well-known data types

Weekend advice:  

1. Copy the latest comp310f10.rmiChat interfaces over to your own rmiChat package and build your code off of that.  
2. Add/modify methods, interfaces as you think are necessary to make the chat system work.   Remember that any changes will have to be eventually applied to everyone in the class!
3. Post change and modification ideas to discussion board and send out e-mail telling everyone to please look at your suggestions.
4. Discuss on Monday and agreed upon changes will be committed to the  comp310f10.rmiChat package.
5. The above process may need to be repeated.
6. In the end, simply change the import statements from your rmiChat package to the  comp310f10.rmiChat package.

© 2010 by Stephen Wong and Scott Rixner