Re: HTTP and MPM support

2019-02-08 Thread Sive Lindmark
Hi!

about André’s post, I agree 100 % .

> I believe that we could all collectively start by making a financial 
> contribution to such a preliminary effort, if that is also what it takes to 
> get it going.
yes!!

Sive

Re: HTTP and MPM support

2019-01-27 Thread Sive Lindmark
Hi William!

Count on us, my firm can sponsor work as I stated before, and also contribute 
setting up test cases and perhaps also do some coding if we have the knowledge 
to do whats needed.
My coders are not used to be part of any open source project, so we can not 
take any leading roll though.

How could a sponsor model work?  

I have followed crypto world for some time now, and they sometimes set up price 
for someone thats achieve a goal. Something we can do here?
 
/Sive  



Re: HTTP and MPM support

2019-01-26 Thread Sive Lindmark
Hi! 

Perhaps in the same boat? Our company can sponsor between $1000 - $1 to a 
project developing modPerl 3 (Perl 6 + stabil mpm-worker/event)

If some more in the boat can tribute also it would be awasame ...

/Sive



Re: HTTP and MPM support

2019-01-25 Thread Sive Lindmark



> On 25 Jan 2019, at 20:00, Michael A. Capone  
> wrote:
> 
> 
> 
> On 1/25/19 10:54 AM, Randolf Richardson wrote:
>>> On 25.01.2019 1modperl@perl.apache.org8:35, John Dunlap wrote:
 I'm in the process of optimizing our web application for performance and 
 one thing that I
 was really excited to try was mod_http2 because it allows the browser to 
 send multiple
 requests through the same TCP connection with compressed headers.
> 
  Are there any plans to support other MPM's? If not, the
 benefits of HTTP2 appear to be permanently out of reach for our mod_perl 
 applications and
 that, honestly, might force us into seriously reevaluating our technology 
 stack. :(
 
>>> Am I allowed to jump into the same thread, and ask about what the general 
>>> status of
>>> mod_perl is, nowadays (if someone knows) ?
> 
>>> (Mind you, for us MPM prefork and HTTP 1.1 are still perfectly ok, but the 
>>> question is
>>> more about the longer-term future).
>>  I'm also curious about this as I anticipate HTTP/2 support becoming
>> a valuable and important feature in the future (the recent updates to
>> mod_perl2 have been good for us).
>> 
>> Randolf Richardson - rand...@inter-corporate.com
>> Inter-Corporate Computer & Network Services, Inc.
>> Beautiful British Columbia, Canada
>> http://www.inter-corporate.com/
>> 
>> 
> I have to add my voice to the growing chorus here.  As it stands, we are 
> forced to choose between mod_perl and HTTP/2.  At the moment, our shop has 
> chosen to keep mod_perl, but I share the above concerns, and I'd rather see 
> mod_perl be ready if there is ever a major cultural shift / push to HTTP/2 in 
> the broader market.

as a owner of a small but quite fast growing company that first used MPW worker 
which was a little bit unstable and then went for prefork and this is working 
very well for now ...but it would be fantastic to have a stable worker for 
http/2, so if someone? can fix it we can probably sponsor part of work for I am 
sure that changing technic cost a lot more …  /Sive

Re: mod_perl: How pass variables (objects) from page to page?

2005-11-15 Thread Sive Lindmark

On 2005-11-15, at 03.11, Peter1 Alvin wrote:

 Please tell me I can do this!
 

 Using mod_perl, how do you keep Perl objects in RAM from page to page?  I don't want to re-instantiate my objects on every page request, and I don't want the overhead of serializing my objects to a persistent store from page to page (I use A LOT of objects).
 

 I've done extensive reseach and I've not found any application space to store objects indefinitly.
 

 I can't believe Perl doesn't support keeping objects in RAM.  This would de-qualify Perl for half of the projects I need to develop.
 

 Peter Alvin


Hi!

Have looked around like you for a solution to this, without finding one and after discussing it internally, we thought that the optimal can be to write a custom reversed modproxy server that talks directly to the perl code ... perhaps as a open software project 

Perhaps there are such project already?   but folks at this list should know :)  ...

Sive



Is there a bug in Apache 2, ModPerl 2 or APR for data larger than 64k?

2005-08-04 Thread Sive Lindmark
Hi!

Have used mod_perl 2.0 and newer  for a while and it have worked very well on Mac OS X and Free BSD servers. Now on a Xserve with Mac Os 10.4 the following happens. Requesting a web page with little contents works okey but an bigger contents the loading always stops in the middle with the following error message in error_log.   

(35)Resource temporarily unavailable: core_output_filter: writing data to the network

The error is coming in different places in the code but always about half the page so searching the web I found some stuff. x-tad-smaller/x-tad-smallerx-tad-smallerThere is a bug in APR 0.9.6 that is present when it is running on Tiger, and shows up when you attempt to check out a file larger than 64K./x-tad-smallerx-tad-smaller /x-tad-smallerhttp://subversion.tigris.org/faq.html#tiger-apr-0.9.6'
x-tad-bigger 
/x-tad-biggerIf this the cause of our problem I sought that by installing the latest versions of mod_perl and apache2 (SERVER_SOFTWARE = Apache/2.1.6 (Unix) mod_perl/2.0.2-dev Perl/v5.8.6) could fix this.  but no 

I also tried setting a environment variable  before configuring Apache and modPerl2 suggested as fix above.
Currently, the best solution is to rebuild Apache from their respective sources, setting the following environment variable before running configure for Apache in Bourne shell syntax, like this: x-tad-smallerac_cv_func_poll=no; export ac_cv_func_poll/x-tad-smaller 

Now I have no more ideas about what to do  any suggestions?
What APR version is there in latest mod_perl?   Can the bug above still be there or ...

Thanks in forehand!
Sive











Re: Is there a bug in Apache 2, ModPerl 2 or APR for data larger than 64k?

2005-08-04 Thread Sive Lindmark
Hi! 

As it seem that the bug is in libapr you should make sure to use the latest. It's possible that you are still using the old library. Try

ldd httpd

and see which libapr.so it links to.
100:/Users/boka/modperl-2.0 root# otool -L /Library/Apache2/bin/httpd
/Library/Apache2/bin/httpd:
/usr/local/apache2/lib/libaprutil-1.0.dylib (compatibility version 2.0.0, current version 2.1.0)
/usr/local/apache2/lib/libexpat.0.dylib (compatibility version 2.0.0, current version 2.0.0)
/usr/lib/libiconv.2.dylib (compatibility version 5.0.0, current version 5.0.0)
/usr/local/apache2/lib/libapr-1.0.dylib (compatibility version 2.0.0, current version 2.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.0.0)
/usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version 92.0.0)

Installed the latest snapshot from APR. x-tad-biggerapr_20050804222905.tar.gz/x-tad-bigger  and after that when building Apache I got an other problem.
x-tad-bigger
/usr/local/apr/build-1/libtool --silent --mode=compile gcc -g -O2-DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp-I/Users/boka/httpd-2.1.6-alpha/srclib/pcre -I. -I/Users/boka/httpd-2.1.6-alpha/os/unix -I/Users/boka/httpd-2.1.6-alpha/server/mpm/prefork -I/Users/boka/httpd-2.1.6-alpha/modules/http -I/Users/boka/httpd-2.1.6-alpha/modules/filters -I/Users/boka/httpd-2.1.6-alpha/modules/proxy -I/Users/boka/httpd-2.1.6-alpha/include -I/Users/boka/httpd-2.1.6-alpha/modules/generators -I/Users/boka/httpd-2.1.6-alpha/modules/mappers -I/usr/local/apr/include/apr-1 -I/usr/local/apache2/include -I/Users/boka/httpd-2.1.6-alpha/modules/proxy/../generators -I/Users/boka/httpd-2.1.6-alpha/modules/ssl -I/Users/boka/httpd-2.1.6-alpha/modules/dav/main  -prefer-non-pic -static -c exports.c  touch exports.lo
exports.c:1572: error: redefinition of 'ap_hack_apr_allocator_create'
exports.c:687: error: previous definition of 'ap_hack_apr_allocator_create' was here
exports.c:1573: error: redefinition of 'ap_hack_apr_allocator_destroy'
exports.c:688: error: previous definition of 'ap_hack_apr_allocator_destroy' was here
/x-tad-bigger
but as the problem is not with modPerl  I think it is best that I take this to the APR mailing list

Thank's for your answer

Hälsningar från Sverige / Sive