I agree with this. There are several methods in Application (and in a few other classes I think) that assume alot about the relationship between the URIs and 'targets'. At the moment, targets can be files in a particular 'context'. With the ideas for flexible URI-to-target mapping and multi-app architectures that have been floated this year it might be time to revisit some of these methods. Tavis
On Thursday 15 November 2001 15:21, Sascha Matzke wrote: > Hi, > > as I worked my way through the sources of WebKit today I > discovered something in Application.py what in my eyes > seems to be a major limitation of the capabilities WebKit > would be able to provide. > > In Application.dispatchRequest() is a check for the existence > of a server-side match for the requested path. > > ssPath = request.serverSidePath() > if ssPath is None: > self.handleBadURL(transaction) > > So why do I think that this is a bad thing... > > Today I tried to implement something I call ActionKit. > That component is a very streamlined URI->Action mapper > as you might know it from the struts framework for Java. > The idea is to map a certain "virtual" URI target to > a specific action class. > > The problem is that naturally those "virtual" targets > don't exist on the file system. So per default there > are handled as BadURL and nothing happens (except for > a 404 ;)) > > My suggestion is that we move the file system stuff were > it (IMO) belongs - into the ServletFactories that handle > physical files. > > > Opinions? > > Sascha > > > _______________________________________________ > Webware-discuss mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/webware-discuss _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
