Gunther Birznieks wrote:
Is this a lot different from PlRPC?
Perhaps this should be a transport layer that is added to PlRPC rather than
creating a brand-new service?
Ideally it would be nice if it were architected with mod_perl and HTTP
being the default mechanism of transport but that
On Wed, 9 Jan 2002, Mark Maunder wrote:
The difference is that AppCluster allows you to call
multiple remote methods on the server (or on multiple
distributed servers) simultaneously. However, I wasn't
aware of PlRPC and I really like the interface i.e. the
way it creates a copy of the
brian moseley wrote:
On Wed, 9 Jan 2002, Mark Maunder wrote:
The difference is that AppCluster allows you to call
multiple remote methods on the server (or on multiple
distributed servers) simultaneously. However, I wasn't
aware of PlRPC and I really like the interface i.e. the
way
On Wed, 9 Jan 2002, Mark Maunder wrote:
Well, I guess two methods could be added to the client
object. One to add a concurrent request to be called
(register_request()) and one to send all registered
requests concurrently. I'm not the author though, so
you'll have to chat to Jochen about
brian moseley wrote:
On Wed, 9 Jan 2002, Mark Maunder wrote:
Well, I guess two methods could be added to the client
object. One to add a concurrent request to be called
(register_request()) and one to send all registered
requests concurrently. I'm not the author though, so
you'll
Apache::AppCluster is now in CPAN and can be accessed at:
http://search.cpan.org/search?dist=Apache-AppCluster
This consists of a client and server module that can be used to develop
mod_perl clustered web services. A client application can make multiple
simultaneous API calls to a mod_perl
Hi all,
I'm about to post this module to CPAN. Please take a look and let me
know if you think this is appropriate for the Apache::* namespace and if
you have any problems with it ('make test' is quite comprehensive).
The module is available from:
