No, because webwork is not supposed to be 'use this to solve all your needs'.
It provides an important part of the overall solution. It's trivial to slap on a security system on top of it, and webwork doesn't need to be aware of it and can function perfectly well within it. If there's such a strong demand for such a system, it could be a separate project that should be webwork aware, but webwork-core if you will need not be aware of the extra layer Quoting boxed <[EMAIL PROTECTED]>: > > Why can't you write a filter that reads a config file and checks the > > incoming URL to see if it is requesting an action that you would like to > > restrict access to? How does that solution not solve your problem? > > Seems to me like this is asked for a lot, shouldn't a solution like the one > you suggested be included in WebWork? > > // Anders Hovmöller > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ApacheCon, November 18-21 in > Las Vegas (supported by COMDEX), the only Apache event to be > fully supported by the ASF. http://www.apachecon.com > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
