Jon, I think you need to give more information about your actual requirements. As I already mentioned, I have a simple servlet which serves up images by ID and the ID is passed in via a HTTP POST (although originally I had it going via a HTTP GET and you could do this too).
I don't see why one would need access to the Wicket session...? Again, it isn't clear to me what your actual requirements are. If you simply have a client-server architecture, why not code up all your server components as servlets to send image data, etc?
I think it only makes sense to move this into Wicket if the client is an ordinary web browser... but then I really don't see what you could accomplish with such an architecture...
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
