Hi Zubair, Diogo:
I hope you guys could join and figure out the detailed message format
for the communication interfaces. :)
In the spec, we have decided to use RESTful webservice and RPC call for
the communications. Now the
form of RPC call is somewhat obscure, we need to make a clearly defined
message format. Do you think we
should still use protobuf, or json/xml, or customized binary/text format?
This is important.
At first, there should be an authentication process after connected.
Then we use the negotiated
symmetric key to encrypt the following messages. The messages will be in
pair, like Request/Response.
For a request, there should be a RPC function name and then the parameters,
finally maybe end with a checksum.
And for a response, it will indicate which request it response to, and then
the result.
If we use protobuf, then we need to put the function name out of the
message. So after the agent read the name,
it will generate a proper class for the message.
How do you think which one we should choose?
Regards
--
Zhongjie Wang
Master Candidate
Computer System Architecture
Peking University, China
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Umit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/umit-devel
