In spite of all this, I've been running Shindig at /shindig for months now
under Jetty. The only thing I needed to do was set up a Jetty rewrite rule as
follows:
<Call name="addRule">
<Arg>
<New class="org.mortbay.jetty.handler.rewrite.RewriteRegexRule">
<Set name="regex">/(social|gadgets)/(.*)</Set>
<Set name="replacement">/shindig/$1/$2</Set>
</New>
</Arg>
</Call>
-Dave
-----Original Message-----
From: Eric Tschetter [mailto:[email protected]]
Sent: Wednesday, December 17, 2008 6:54 PM
To: [email protected]
Subject: Re: shindig using non root context
> Open source development is however also a demand driven development model,
> so if this is an itch you want to scratch, patches are welcome!
touché
To be more clear about why I was concerned, I consider integration
points a part of backwards compatibility in a release and I am
wondering if a 1.0.0 release were made and then changes were made to
how one integrates, could it be a minor version change or would it
have to be a major? It seems like the change would either require
support for the old integration method to be a minor or it would
equate to a major release. That is, someone might not necessarily be
able to just drop in a new JAR and have it work.
Then again, the Apache APR documentation
("http://apr.apache.org/versioning.html";) seems to only talk about
functional APIs and not necessarily configuration, so maybe I am
making more out of it than it deserves.
--Eric Tschetter
