prefork is, currently, is still the only MPM which works reliably for us.
The others segfault at seemingly random intervals.
On Sun, Jul 29, 2018 at 8:18 PM, Paul Silevitch <p...@silevitch.com> wrote:
> Like Dr. James Smith, I'm hooking into multiple handlers and using
> filters. I'm currently using prefork but thought people were using worker
> in production (assuming the application is thread safe). Is that not the
> case?
>
> Paul
>
> On Sat, Jun 9, 2018 at 7:03 AM, Dr James Smith <j...@sanger.ac.uk> wrote:
>
>> No - because of the way it works it handles the request inside apache -
>> the worker/event systems work by handing the request back to another
>> process or processes in the background which handles the request and then
>> returns - which is where the problem lies in the fact that you are
>> effectively adding a proxy layer between the web-request and the actual
>> perl process...
>>
>> It limits what you can do with Plack when it comes to handling aspects of
>> the request which are better handled outside the main response phase {e.g.
>> re-write, logging, cleanup etc} which limits functionality - most people
>> who just use response handlers do not see this issue. But we hook into
>> about 10 phases of the apache process ...
>>
>> On 08/06/2018 02:08, John Dunlap wrote:
>>
>> Does using mod_perl properly allow you to use mpm_event or mpm_worker?
>>
>> On Thu, Jun 7, 2018 at 9:19 PM, Dr James Smith <j...@sanger.ac.uk> wrote:
>>
>>> Unfortunately Plack (and Catalyst especially) are a fairly poor
>>> comparison to using mod_perl properly {unfortunately very few people do so}
>>> I've looked at Dancer and Catalyst - both are OK at what they do - but they
>>> don't really handle things in the really clean easy way that mod_perl does
>>> {if you attach code to the right handlers/filters} meaning chopping in and
>>> changing code can be quite difficult in them.
>>>
>>> Both are good for simplish applications {yes and I've seen complex apps
>>> written in them as well - but they usually need a lot more hardware support
>>> than the equivalent mod_perl app to cope with demand}
>>>
>>> Unfortunately writing good mod_perl apps is hard - and so few mod_perl
>>> apps really make use of the underlying framework properly - effectively
>>> using it for code caching and not much else
>>>
>>>
>>>
>>> On 07/06/2018 19:24, David Hodgkinson wrote:
>>>
>>> Moving your method handlers to the framework.
>>>
>>> I like catalyst. Stand on the shoulders of giants. Mojolicious makes me
>>> itch.
>>>
>>> On 7 Jun 2018, at 19:21, John Dunlap <j...@lariat.co> wrote:
>>>
>>> What is involved in porting an application from mod_perl to starman?
>>>
>>> Throwing away logic and logical structure and replacing it with a much
>>> less flexible approach...
>>>
>>> On Thu, Jun 7, 2018 at 6:18 PM, Clive Eisen <cl...@hildebrand.co.uk>
>>> wrote:
>>>
>>>> On 7 Jun 2018, at 19:13, David Hodgkinson <daveh...@gmail.com> wrote:
>>>>
>>>> No. Different concept.
>>>>
>>>> On 7 Jun 2018, at 18:52, John Dunlap <j...@lariat.co> wrote:
>>>>
>>>> Is Plack backwards compatible with mod_perl?
>>>>
>>>> On Thu, Jun 7, 2018 at 5:44 PM, David Hodgkinson <daveh...@gmail.com>
>>>> wrote:
>>>>
>>>>> We’re all about the Plack these days.
>>>>>
>>>>>
>>>> This.
>>>>
>>>> We have moved entirely to
>>>>
>>>> nginx (doing the ssl where appropriate) -> starman (which uses plack)
>>>> and Dancer2
>>>>
>>>> Life is a LOT better
>>>>
>>>> —
>>>> Clive
>>>>
>>>>
>>>
>>>
>>> --
>>> John Dunlap
>>> *CTO | Lariat *
>>>
>>> *Direct:*
>>> *j...@lariat.co <j...@lariat.co>*
>>>
>>> * Customer Service:*
>>> 877.268.6667
>>> supp...@lariat.co
>>>
>>>
>>>
>>> -- The Wellcome Sanger Institute is operated by Genome Research Limited,
>>> a charity registered in England with number 1021457 and a company
>>> registered in England with number 2742969, whose registered office is 215
>>> Euston Road, London, NW1 2BE
>>> <https://maps.google.com/?q=215+Euston+Road,+London,+NW1+2BE&entry=gmail&source=g>.
>>>
>>>
>>
>>
>>
>> --
>> John Dunlap
>> *CTO | Lariat *
>>
>> *Direct:*
>> *j...@lariat.co <j...@lariat.co>*
>>
>> * Customer Service:*
>> 877.268.6667
>> supp...@lariat.co
>>
>>
>>
>> -- The Wellcome Sanger Institute is operated by Genome Research Limited,
>> a charity registered in England with number 1021457 and a company
>> registered in England with number 2742969, whose registered office is 215
>> Euston Road, London, NW1 2BE
>> <https://maps.google.com/?q=215+Euston+Road,+London,+NW1+2BE&entry=gmail&source=g>.
>>
>>
>
>
--
John Dunlap
*CTO | Lariat *
*Direct:*
*j...@lariat.co <j...@lariat.co>*
*Customer Service:*
877.268.6667
supp...@lariat.co
