[Agendaware-dev-server] XML Defs

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

Zack,
I noticed where you posted some ideas about the XML
APIs to the be used and I had a suggestion. The root
elements you have are a good place to start, but I
thought it may be clearer if above those elements we
had a tag of something like "Request" and "Reply" to
identify the type of communication this is. For
example, on the server side, if server to server
communication is happening, the server will need to
know if the incoming XML is a request for information
or a reply to a previously sent request.  The client
will only receive "Reply" XML docs, but I think these
tags make the communication (at least when viewed by
an XML viewer or something during testing/debugging) a
bit clearer what is actually happening. 

I think the best thing to do at this point is to get
the API down first.  Once we determine the calls that
can be made back and forth between the client and
server, we can then start designing/coding the server
and client to handle those requests and work
independently.  I'll start looking at the XML doc you
started and try to really define the kind
queries/responses/calls that need to be made between
the client and server.  

Just for simplicity, is there any particular component
you would like to look at first (email,calendar,im,
etc. . )?  I think email would be the logical start
since that's sort of the basis for this whole thing.

Anybody else have any thoughts?


__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com