in reply to Re: [FCGI.pm] - not threads-safe?
in thread [FCGI.pm] - not threads-safe?

I need FCGI.pm in threads because this is a single way to create preforking fcgi server, which can process parallel requests under window.

FCGI.pm just listen socket, accept connection and populate the environment hash.

Why it could never be threads safe? It's perfectly work in threads under MSWin and Linux, except segfault when thread has been destroyed.

Replies are listed 'Best First'.
Re^3: [FCGI.pm] - not threads-safe?
by BrowserUk (Patriarch) on Aug 20, 2013 at 13:13 UTC
    It's perfectly work in threads ... except segfault when thread

    Tada!

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

      It mean, that FCGI.pm MUST have properly implemented cleanup routine, that cleanup used resources in right way, and a public method to call this routine.

      My question was - is there anybody solve this problem?
[reply]
        It mean, that FCGI.pm MUST have properly implemented cleanup routine,

        Why "MUST" it? Because you said so? It DOESN'T, and there is a good reason:

        It makes no sense to use threads with FCGI

        I'm not going to explain that. YOU need to go out and read up on FastCGI and FCGI to understand why that is so.

        With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom