On Wed, Oct 31, 2012 at 8:41 AM, Devin Austin <devin.aus...@gmail.com> wrote:
> On Wed, Oct 31, 2012 at 3:50 AM, Tim Anderson <tja...@gmail.com> wrote:
>> 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.

>> Does anyone have experience with doing something like this?  I'd appreciate
>> any insight or direction.
> This would be fairly do-able if you used REST for inter-app
> communication.  Or something like Message::Passing, which allows you
> to send a "message" to a queue, which could be subscribed to from both
> ends, thus allowing the apps to talk to each other.
> If the Catalyst app is acting as a proxy to the servlets, I would
> think you could do a pretty regular
> authentication/authorization/session set up with it and just pass
> along whatever other info you need to the servlets via the
> aforementioned means.

Another approach worth considering is to wrap the servlets up in a
model. This often takes a bit longer and more thinking in the set-up
phase but will give you code that is easier to reuse in other places.
I've done this kind of problem both ways and either is fine but I'd
lean to the model. You would end up with something you could run with

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