Hi, Ian Bicking wrote:
> Right, but that leaves the extension in the URL, which is something > Webware intentionally does not do. And, like I said, it makes the > framework easier -- but I still think it's worth it not to use them. Ok... I think there are two kinds of URLs. Those which are viewable and those which are not. I tend to design my applications after the MVC paradigm. So I want to have Models, Views and Controllers. The only thing a user should be able to see are the Views. My ActionKit (as every other action2URI mapping package out there) just provides a way for the application to internally adress the desired action through an controller. Think of an view named http://www.somesite.tld/Application/myView, which contains a form. Where to I want that form to send its data? To another viewable URL? No. I want to submit that form to a certain action which maybe manipulates the submited data and than forwards the request to another (or the same) viewable URL. So what is wrong with the approach to submit the form in a way like <form action="doSomething.yaa" method="post"> .... - no matter where you are in your "webpath", as the extension .yaa is automatically mapped to the controller servlet and never seen by the User? Sascha _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
