• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [OT] Versioning and compatibility checking
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [OT] Versioning and compatibility checking


  • Subject: Re: [OT] Versioning and compatibility checking
  • From: David Avendasora <email@hidden>
  • Date: Mon, 30 Jun 2008 11:08:37 -0400


On Jun 30, 2008, at 10:28 AM, Florijan Stamenkovic wrote:

Hi all,


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).

What kinds of things are you trying to catch? Things like if a invokeRemoteMethod("clientSideRequestFoo", keys[], values[]) is called that it will verify that the clientSideRequestFoo with the defined parameters actually exists? That would be nice.


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.

Wow. You are the Mike Schrag of JC! First JBND, now this? (no offense to all the other Wonder/Wolips contributors)

It is not my intention at the moment to deal with server app <-> database compatibility. Besides, I believe this has been addressed in WOnder already, no?

If you are referring to Migrations updating the DB at startup to match application-defined schema and some basic data massaging, yes, it does.


I have some ideas, but also some questions:
1. Does anyone do this, if so, can I have a look?
2. Anybody wants to share some general experience with this sort of stuff?
3. Any pointers to third party libraries with a similar purpose + recommendations?
4. Any design suggestions (if someone is interested, we can discuss this in more detail off list), or best practices?

Why off list? The more this type of thing is discussed on-list the more people may chime in with similar non-JC ideas.

5. Anything else?


F _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: [OT] Versioning and compatibility checking
      • From: Florijan Stamenkovic <email@hidden>
References: 
 >[OT] Versioning and compatibility checking (From: Florijan Stamenkovic <email@hidden>)

  • Prev by Date: Re: Java Code Coverage for Eclipse
  • Next by Date: Fwd: WebObjects take on GWT?
  • Previous by thread: [OT] Versioning and compatibility checking
  • Next by thread: Re: [OT] Versioning and compatibility checking
  • Index(es):
    • Date
    • Thread