Janne Jalkanen wrote:
http://www.acme.org/wiki/pages/PageName/?action=get
http://www.acme.org/wiki/pages/PageName/?action=edit
http://www.acme.org/wiki/pages/PageName/?action=put
http://www.acme.org/wiki/pages/?action=search&q=term
The ShortURLConstructor does just this.
Unfortunately, it's not very well tested, and is known to break some
things, like FCK and WikiWizard.
And I've never once got the ShortURLConstructor to work reliably
on any system (Apache/Tomcat or Jetty) I've used, after much time
and frustration. I don't think that's uncommon, and on looking at
the code I've not figured out what was going wrong. I like the
idea of having a front end request manager that acts as a web
service layer to the wiki, especially if it is in effect modular.
I have a strong requirement for a REST-ful scheme, with some
flexibility on the definition of REST-ful. One thing I didn't
mention (and Andrew's Stripes proposal might provide) is a
web service approach to both the JSPWiki instance *and* a
second web service that could either be a layer on top of
JSPWiki or literally a separate application that accessed the
wiki's repository. Since it needs to share the same JVM likely
a layer, and if it was able to hand requests off to JSPWiki
*or* something I've written, well, that's basically what I'm
looking for in a nutshell.
So the Stripes approach is quite exciting, really.
Murray
...........................................................................
Murray Altheim <murray07 at altheim.com> === = =
http://www.altheim.com/murray/ = = ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = =
Boundless wind and moon - the eye within eyes,
Inexhaustible heaven and earth - the light beyond light,
The willow dark, the flower bright - ten thousand houses,
Knock at any door - there's one who will respond.
-- The Blue Cliff Record
