Re: Mysql handle not in asynchronous mode

[punkish]

in reply to Mysql handle not in asynchronous mode

Strange... a simple script like so works like a champ... no async nonsense, no errors. All 1000 requests are effortlessly returned by the same set up.

use LWP::UserAgent;

my $BBOX = "-96.09299316406248+38.96034339396338%2C+-83.39279785156248
++38.96034339396338%2C+-83.39279785156248+44.33256692562997%2C+-96.092
[phone]+44.33256692562997%2C+-96.09299316406248+38.96034339396338
+";

for (1 .. 1000) {
    open my $fh, ">>", 'foo.txt';
    
    my $ua = LWP::UserAgent->new;
    $ua->agent("MyApp/0.1 ");
    
    my $req = HTTP::Request->new(GET => "http://localhost:5001/points.
+json?callback=foo&BBOX=$BBOX");
    my $res = $ua->request($req);
    
    # Check the outcome of the response
    if ($res->is_success) {
        say $fh $res->content;
    }
    else {
        say $fh $res->status_line;
    }
    
    close $fh;
}

So, it seems that both MySQL and Starman are very capable of handling this. THe only element missing here is Dancer, and the browser. Thoughts anyone?