I have a handful of java servlets that I would like to 'front-end' with my
Catalyst application, essentially using Catalyst to provide
authentication/authorization before passing along the browser requests to
the servlet.  I don't need session information in the servlet, and I'm
willing to leave the servlet unsecured on an obscure port (network
protected, of course) in order to allow Catalyst to more easily interact
with it. In my mind, I see Catalyst behaving as a proxy, managing the
entire conversation, but I'd also be open to some kind of redirection

Does anyone have experience with doing something like this?  I'd appreciate
any insight or direction.

List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

Reply via email to