You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Sim IJskes - QCG <si...@qcg.nl> on 2010/09/29 10:59:49 UTC
Re: Towards Internet Jini Services (versioning)
On 29-09-10 10:26, Zoltan Juhasz wrote:
> The API approach that Jini takes requires up-front design work and same say
> these systems will inherently be brittle. I think versioning is a problem in
> both approaches. What is more interesting in the API approach is that
Are you refering to the scenario, where the server definition of the API
is updated, and the client is still using the old one?
An easy solution for this, would be the simultaneous deployment of both
server and client code.
Adding a method to a class, should pose no problem, changing class
hierachies does.
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397