in reply to Re^2: Can two separate responses be sent to the client's browser from Perl, such as via fork{}?
in thread Can two separate responses be sent to the client's browser from Perl, such as via fork{}?

The server returns the PDF in about 6-7 seconds for a 330+ page book. This is quite tolerable, and is in no danger of timeouts.

For requests arriving serially. Try 20 in parallel and see what happens.

🦛

  • Comment on Re^3: Can two separate responses be sent to the client's browser from Perl, such as via fork{}?

Replies are listed 'Best First'.
Re^4: Can two separate responses be sent to the client's browser from Perl, such as via fork{}?
by Polyglot (Chaplain) on Oct 17, 2023 at 10:27 UTC
    I imagine you're quite right. I am unconcerned, however, because I am planning this for a niche group, and the average requests might be fewer than two per day (it might go a week or more between "bursts" of activity, and likely will have only a handful of individuals even accessing the site--fewer than 20, to be sure).

    Now, once put online could it go "viral"? Perhaps. In such a case I would probably have to put it behind a login. But I really do not expect to have much trouble with traffic, at least not for some time.

    Blessings,

    ~Polyglot~

[reply]

In Section Seekers of Perl Wisdom