Webware for Python

Tripp Lilley wrote:

>Is there a straightforward way to do this in the latest CVS (or any recent
>release)? If so, has it "always" been so, or is it a recent addition?
>  
>
I believe this is what the "extrapath" setting is for. I've used it, and 
I think Ian even "fixed" it recently.

It's possible that it gets trumped if the filepath does actually exist, 
but that's pretty easy to avoid.

For example, in /your/ example:

http://webware.example.com/dav/some/file/path.txt

There are two ways to get extraPath working:

1. /dav/index.py is the actual servlet that eats the rest of the URL. 
I've done this; it works.
2. /dav.py is the actual servlet; I think Ian's recent fix does make 
this work, but he'd have to weigh in on that.

Now, what I was worried about above, is that if /dav/some/file is 
actually ON the filesystem, it might go there instead of to the 
short-circuited servlet.

On Fri, 27 Sep 2002, Matthew J. Feifarek wrote:

> I believe this is what the "extrapath" setting is for. I've used it, and
> I think Ian even "fixed" it recently.

Ah. Cool. I skimmed the configs and saw things like extensionsToIgnore,
etc., but didn't catch ExtraPath. Thanks :)


> Now, what I was worried about above, is that if /dav/some/file is
> actually ON the filesystem, it might go there instead of to the
> short-circuited servlet.

Does either of the ExtraPath methods you described (/dav/index.py or
/dav.py) avoid this? Obviously, since I want the DAV servlet to handle
reads -and- writes to those paths, even if they exist, it's pretty
important that I trap all calls down under /dav/... :)

(BTW: yes, I'm working on a DAVKit for Webware :) ).

On Fri, 2002-09-27 at 13:09, Tripp Lilley wrote:
> > Now, what I was worried about above, is that if /dav/some/file is
> > actually ON the filesystem, it might go there instead of to the
> > short-circuited servlet.
> 
> Does either of the ExtraPath methods you described (/dav/index.py or
> /dav.py) avoid this? Obviously, since I want the DAV servlet to handle
> reads -and- writes to those paths, even if they exist, it's pretty
> important that I trap all calls down under /dav/... :)
> 
> (BTW: yes, I'm working on a DAVKit for Webware :) ).

Then you should check out DAVKit: 
  http://www.colorstudy.com/software/webware/DAVKit-0.2.tar.gz
:)

It doesn't deal with erroneous situations that well, and it requires a
somewhat new servlet layout (i.e., different than WebKit.Page -- that
uses exceptions for more logic).  But I've tested it with cadaver and
Web Folders, and it basically works.

You do need CVS Webware for the extraURLPath fix, and you need to put
'UseNewPathAlgorithm': 1 into Application.config.

  Ian

On 27 Sep 2002, Ian Bicking wrote:

> Then you should check out DAVKit:
>   http://www.colorstudy.com/software/webware/DAVKit-0.2.tar.gz

Oh. Sweet. Less work, more play :) Now I just have to drag this beastly
app kicking and screaming into the latest Webware, Cheetah, MiddleKit, and
so forth. Sigh :)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tripp Lilley <tlilley@...> writes:

> Does either of the ExtraPath methods you described (/dav/index.py or
> /dav.py) avoid this? Obviously, since I want the DAV servlet to handle
> reads -and- writes to those paths, even if they exist, it's pretty
> important that I trap all calls down under /dav/... :)

If you find problems/solutions for this (the extra-path stuff
more-or-less does what I want, but I haven't extensively explored it
yet), please post such problems. I am also working on a similar
layout.

I may also go about implementing some type of URL-proxy object, which
would be set into the Application and allow arbitrary re-mapping of
URLs to servlets. The default would obviously do whatever happens now,
but I would like to intelligently redirect some URLs based on
non-trivial information (i.e. not achievable with mod_rewrite regular
expressions or similar).

Cheers,

- -- 
mike@...
<URL:http://www.mike-warren.com>
gpg --keyserver 80.71.227.37 --recv-key 579911BD
87F2 4D98 BDB0 0E90 EE2A 0CF9 1087 0884 5799 11BD


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard <http://www.gnupg.org/>

iD8DBQE9mhRLEIcIhFeZEb0RApvHAKCmAuPtFoZpzmoqvkxDc8s9gbTGjQCgjEim
BF1R61MIKhOYpPoaX2cjJgA=
=izBl
-----END PGP SIGNATURE-----