LIfeguard as a method invocation abstraction

[shlomo....@gmail.com]

Hi David,

I run lifeguard Services in three different locations:
A. on separate instances via the pool manager
B. locally on the same machine as the web application, without a pool
manager but in a separate process from the web app
C. in the same process as the web application, where the application
code makes direct method calls into the guts of the Service (without
the SQS message passing, and "underneath" the
AbstractBaseService.execute method)

I would like to use the same invocation mechanism for my code
regardless of deployment location. Using the Ingestors makes sense for
A and B, but for C (in-process services) it does not. Ideally,
something that can be configured at deployment-time to use the
appropriate invocation binding.

Can you recommend something that could provide such an
abstraction-of-the-invocation layer?

Thanks.

.. Shlomo