On 01/07/2008, at 6:39 AM, Andrew Lindesay wrote:
Hello Florijan;
I use a "compatibility integer" that gets matched between the client
and the server's base-endpoint. This works well for the situation
where you have one or two pieces of (in my case JSON-RPC) client
software, but as the number of different pieces of client software
grows, it then calls for a roll-out of everything for each update to
this "compatibility integer". So far, I have not seen an easy
solution to this issue, but have also not had the opportunity to
invest any serious time into it because in my cases it is manageable.
Yeah, we have the same situation. It's essentially a schema
compatibility integer.
Perhaps a major and minor version would work where major versions have
to match and minor versions are insignificant (e.g., for bug fixes)
I am about to implement a JavaClient focused versioning system to
evaluate the compatibility between the client and the server during
client startup. It is something that is a requirement in our
situation (JC + JBND apps, separated server client projects etc).
Also note that this will be the starting point for WOJCKit, an open
source project where I plan to put this sort of generic stuff.
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
