[Cosmo-dev] proposal for backwards compatibility issue
mikeal at osafoundation.org
Wed Jan 31 15:24:08 PST 2007
> adam has opened bug 7948
> (<https://bugzilla.osafoundation.org/show_bug.cgi?id=7948>) which
> covers the dav url backwards compatibility issue we've been
> we have never guaranteed nor made real effort to provide backwards
> compatibility for anybody other than jared and his users; we wrote the
> 0.6 migration tool for him alone. i think we'd be spending our time
> incorrectly by worrying about backwards compatibility before preview
> for anybody other than jared.
> as i see it, we have 3 options for solving the problem:
> 1) make cosmo treat /dav and /home urls as indistinguishable from one
> another. this will require refactoring of a core jcr-server class and
> will have a ripple effect throughout jcr-server and the cosmo dav code
> 2) write a servlet that accepts /home requests and forwards or
> redirects them to the equivalent /dav urls. this is essentially
> re-implementing the fundamentals of mod_rewrite in java. it adds java
> code that we have to test and then maintain for some amount of time.
> 3) use mod_rewrite in the reverse proxy to replace /home with /dav in
> the urls of requests proxied to cosmo.
> i propose that we go with option 3. this is the simplest solution and
> is owned by osaf.us, the customer with interest in backwards
> compatibility. the recipe can easily be shared with qa for applying to
> their test environments.
What was the reason for changing it in the first place? I apologize
if I failed to see this out on the list, which is likely.
And how much of a hit would it be to just change the dav path back
to /home until the next release?
It seems a little too late in the schedule to change something so
fundamental in the first place, but if it comes down to it I'm in
favor of option 3 above 1 and 2 at this stage in the release as it
will have the least code impact.
More information about the cosmo-dev