[Agendaware-dev-client] Dev Question

[Shane T. <tur...@ya...>]

Hey guys, just had an idea and wanted run it by you.

Currently when developing the server, I'm continually testing
the XML comms to insure that I didn't break anything, etc . .
I was wondering if anyone would object to the server side 
also maintaining the Java side of the communications stuff.
Not everything, just mainly the code dealing with generating, 
receiving and decoding the XML communcations. (Right now, it 
would by the CommsParser class that's defined on the client side)
This would also help me as while I was writing the server and developing
the comms, I could update the Java side comms to match and then use those
to do my testing and insure that the testing programs I'm using (that are
written with the Java comms) would be re-used by the client code.

I'm thinking that if we decide to do this, we could create some well
defined interfaces/classes to be used by the client and as along as
the interfaces remain constant the client could be shielded from the 
communications side as long as the server side keeps the comms current.
(With, of course, suggestions or additions for client guys).

Also, while I was prototyping some stuff for an admin GUI, I started
thinking that I would want to reuse the comms stuff you guys had
instead of creating my own.

Thinking it would look something like this, where the 
horizontal lines represent the insulating layers between
the interfaces.  Client would use/maintain the top layer, 
and server would maintain the bottom layer. 

    Directory Services | Mail | Calendar | Admin
-------------------------------------------------------------
    DirComms  |  Mail Comms |  Calendar Comms | Admin Comms

(Another reason is that I'm getting a craving to do some Java
and thought this would be a good way)  :-)  

How does this sound guys???

__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/