On 14-02-11 13:48, Dan Creswell wrote:
Serialize by URL? Probably - certainly have to express contact details and
this is one way to do it. DNS or similar is also somewhat possible with SRV
records and such.
Ha! :) If by URI, then a ref to SRV is easily extended.
What do we validate on going from dynamic structures to statically typed?
Closest I can get is that service and client must understand each others
contract. They may or may not bother with enforcement of such a contract and
thus they may or may not validate.
Exactly. The contract on exchanging the data would be the typing. Do you
see a recursive serialisation right down to the value objects and
primitives, or do you foresee shortcuts?
Not worried about the verbosity? Binary is so much smaller isnt it?
Do you envision a multi language/platform solution here?
I certainly envision multiple platforms. Multi-language kind of falls out as
a gimme, once one drops away the requirement for movable code. As I said
elsewhere, that doesn't mean movable code cannot still be used. No reason
one couldn't build such a layer in front of REST services if that's "nicer"
in various cases.
Until someone starts coding a java bytecode to python/javascript
translator and starts serving these :).
Dont you see this all ending up in river running on a SOAP-size like RPC
mechanism?
But the main gist of your vision is the replacement of the RPC
mechanism, right?
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
