Hi folks.

In a nutshell, how can you make URL path components become arguments to the
servlet? I thought I saw this someplace in the docs, but I've combed them
and combed them, and can't find it anymore. Maybe I imagined it.

I know that I can do this with the mod_urlrewrite in apache, but let's say
I'd rather do it completely in webware...

The reliance on actual file directories seems cumbersome, given the
sophistication of the application server. If you're not serving documents,
why must you serve from directories?

Here's what I want to do:

I have a simple application that is an online photo gallery. There are three
page types: artist, gallery, and image. An artist contains 'n' galleries, a
gallery contains 'm' images. All of the actual content that's painted into
HTML is in config files or dictionaries or something similar. The
Page()-based servlets merely handle all the back-end details.

Assuming I've set my default Context to this app, I've got a REAL
path/context of http://localhost/galleryApp.py where galleryApp.py is the
servlet that subclasses Page.

A querystring representation of a gallery would be something like:
http://localhost/galleryApp.py?gallery=1

and a querystring representation of an image would be something like:
http://localhost/galleryApp.py?gallery=1&image=3

(many options on this of course).

What I WANT to do is this:

http://localhost/artistName for an artist page,
http://localhost/artistName/gallery1 for a gallery page, and
http://localhost/artistName/gallery1/image3 for an image page

in each case, "galleryApp.py" servlet would be instantiated with the
arguments that follow "localhost" in the URLs... giving the servlet enough
context to build state and choose content.

Any ideas?

Thanks!





_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to