This is not Jon's argument, I do not believe, but an argument that I
think is valid. Let us say that your images served up by your servlet
are generated charts, such as the relative wages of employees. You
wouldn't want just anyone to be able to access this data unless they had
authenticated successfully. In order to determine whether they have
authenticated, you would need to check the wicket session.
Fair enough. Though I still think that Jon's proposal is not generic
enough. Who says I necessarily want this URL syntax?
http://<host>/app/customResource/<type>/<id>
In my application's case, it is far more complex than that. For
example, when someone requests an image, not only do they have to pass
in an ID but the dimensions (width, height) they're looking for etc... I
opted for sending an XML document with my HTTP POST which allows me to
have complex representations instead of the linear HTTP GET style url.
The general proposal might be a good one, but the proposed design of
the solution seems like a total disaster to me. Maybe Wicket should
provide hooks necessary for this sort of problem, but it should not
provide a specific URL structure and methods like Jon was saying because
then you're making an assumption on the domain objects (i.e. that they
rely only on "type" and "id").
Please, focus on hooks, not on specific implementations. Just my 2
cents...
Gili
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
