To make things simple, I created following methods using REST action class.
Once, I call srv_setup it returns me ok quickly
after that If I can srv_status or srv_setup, it goes on wait until that
sleep 1000, finishes
sub srv_setup :Local :ActionClass('REST') {
my ($self, $c) = @_;
here is the script which start
[info] Srvm powered by Catalyst 5.90019
2013/03/05-15:53:51 Starman::Server (type Net::Server::PreFork) starting!
pid(4862)
Resolved [*]:3000 to [0.0.0.0]:3000, IPv4
Binding to TCP port 3000 on host 0.0.0.0 with IPv4
Setting gid to 0 0 0 1 2 3 4 6 10
Starman:
Hi -
On Sun, Mar 3, 2013, at 08:44 PM, linuxsupport wrote:
I tried Catalyst::Plugin::RunAfterRequest, when I send request to the app,
it returns fine but it does not accept any other request after that until that
sub routine finishes.
By default the test server runs a single process, so that
Yes, I know that and tried with -f option, but result was same.
On Mon, Mar 4, 2013 at 9:35 PM, Larry Leszczynski lar...@emailplus.orgwrote:
Hi -
On Sun, Mar 3, 2013, at 08:44 PM, linuxsupport wrote:
I tried Catalyst::Plugin::RunAfterRequest, when I send request to the
app,
it returns
On 4 Mar 2013, at 17:14, linuxsupport lin.supp...@gmail.com wrote:
Yes, I know that and tried with -f option, but result was same.
No other ideas. Some code you haven't shown us doesn't work as you expect - we
can't really do anything other than guess at this point :)
Cheers
t0m
I do not have any suggestions about the App1 to App2 hand off
but perhaps my technique for handling async/long running requests
will help.
I solved my async requirements by using Catalyst::Plugin::Cache
and Catalyst::Plugin::RunAfterRequest.
First off, I have my catalyst apps setup to run as
On Sun, Feb 24, 2013 at 8:16 AM, James R. Leu j...@mindspring.com wrote:
I do not have any suggestions about the App1 to App2 hand off
but perhaps my technique for handling async/long running requests
will help.
I solved my async requirements by using Catalyst::Plugin::Cache
and
any other idea on this?
On Sat, Feb 23, 2013 at 12:31 PM, Francisco Obispo fobi...@isc.org wrote:
I would probably use a message queue.
Have you looked into RabbitMQ ?
App 1 would be the producer, and you would have a consumer, responsible
for performing the operation on App 2.
On
I would probably use a message queue.
Have you looked into RabbitMQ ?
App 1 would be the producer, and you would have a consumer, responsible for
performing the operation on App 2.
On Feb 22, 2013, at 10:40 PM, linuxsupport lin.supp...@gmail.com wrote:
Hi All,
I need your help on the
