[Bese-devel] Re: bese-devel Digest, Vol 22, Issue 12

[Robert Marlow]

Yeah, I'd say regular expressions would be the general case and
non-regexp entry points a special case optimisation. So I vote for (1)
too.

I'm not sure how useful non-regexp entry points would be other than
for optimisation and perhaps simple use of regexp-sensitive
characters. If they are useful, perhaps we need several subclasses of
entry points to handle each type. If they're useful it would seem that
both types may be wanted in the same web-app, in which case having to
define two separate application instances may be more clumsy than just
defining the difference at the entry points themselves (if I'm correct
that you plan on only having the difference coded into the application
class).

Of course if they're no longer useful, which is probably the case,
just ignore me :)


At Thu, 13 Oct 2005 15:58:26 -0700,
Mac Chan wrote:
> 
> Another vote for 1). It's almost inevitable that you need to use regex
> on web apps.
> And I love Edi's packages, they all come with *excellent* documentation.
> 
> > 1) builtin standard ucw feature. this means i'll change the method
> >    defined on standard-application and ucw will new gain a new
> >    dependency (cl-ppcre).
> >
> > ---------- Forwarded message ----------
> > From: Vladimir Sekissov <svg at surnet.ru>
> > To: mb at bese.it
> > Date: Thu, 13 Oct 2005 13:45:34 +0600 (YEKST)
> > Subject: Re: [Bese-devel] (defentry-point "a regular expression"
> > Good day,
> >
> > mb> i need to setup some entrypoints which mathes urls defined by a
> > mb> regular expression like "/catalog/\d+/shipping". i could put this in a
> > mb> url parameter, but due to non-technical requrimentes i can't, and i
> > mb> think it makes for a pretty cool (and usefull) extension.
> > mb>
> > mb> the change itself is fairly trivial and requires only a change to the
> > mb> find-entry-point method. there are two different ways to implement
> > mb> this:
> > mb>
> > mb> 1) builtin standard ucw feature. this means i'll change the method
> > mb>    defined on standard-application and ucw will new gain a new
> > mb>    dependency (cl-ppcre).
> >
> > As for me I would prefer this way. CL-PPCRE dependency is not an
> > issue. Handling web-application is mostly handling strings. Handling
> > strings is mostly handling regular expressions. Handling regular
> > expressions in Lisp is mostly CL-PPCRE.
> >
> > mb>
> > mb> 2) a custom application (ala the cookie-session-app). this has the
> > mb>    advantage that users who don't want this feature needn't download
> > mb>    and bother with cl-ppcre but means that users who do want it may
> > mb>    not find it since the examples won't mention it.
> > mb>
> > mb> preferences?
> >
> > Best Regards,
> > Vladimir Sekissov
> >
> >
> >
> > _______________________________________________
> > bese-devel mailing list
> > bese-devel at common-lisp.net
> > http://common-lisp.net/cgi-bin/mailman/listinfo/bese-devel
> >
> >
> >
> _______________________________________________
> bese-devel mailing list
> bese-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/bese-devel
>