Friday, August 04, 2006

Current planning stage

After Thursdays meeting its become difficult to determine exactly how the communication which be achieved between client and server, let alone what will actually be communicated (does it even need to be XML).

The main points are:
  • Everything is, in some way, based around a book object (presumably defined in an XML Schema document).
  • The GUI should be, at least partially, built from the book object.
  • The RDBMS should be, at least partially, built from the book object.
  • Communication is undecided and will involve the most research, things to consider:
    • REST vs SOAP.
    • Sending a valid XML document closely related to the book object or using our own syntax for a request.
    • Allowing a client to query and/or update the database?
    • What can the server return to the client? Search results (how are these orgainised), error messages, etc.

1 Comments:

At Thu Aug 10, 01:49:00 pm 2006, Blogger Aaron Bishell said...

WSDL seems, in a way, suited for this, although perhaps too low level:

http://www.w3schools.com/wsdl/default.asp
http://www.w3schools.com/wsdl/wsdl_ports.asp

"WSDL bindings defines the message format and protocol details for a web service."

I guess we're not really talking about message format though, more like the behavior of client and server.

 

Post a Comment

<< Home