-8<-- Start Bug Report 8<--
1. Problem Description:
This program when run under :
=
#!/usr/bin/perl
use strict;
use threads;
my $thread = threads->create(sub { print "I am a thread"; },undef);
=
Causes a segfault
[Wed F
Hello,
I'm new to the list, although I've read so many of its messages I feel
like I subscribed weeks ago. :) I'm having some problems getting
libapreq2's Apache::Cookie to send out more than one cookie. The same
basic code worked fine in mp1, which makes me think I'm doing something
improperly
[EMAIL PROTECTED] wrote:
-8<-- Start Bug Report 8<--
1. Problem Description:
This program when run under :
=
#!/usr/bin/perl
use strict;
use threads;
my $thread = threads->create(sub { print "I am a thread"; },undef);
=
Thanks, Stas!
On Thu, 2005-02-03 at 02:51, Stas Bekman wrote:
>
> Looks good to me. IMHO I'd spend the little possible time on the history.
> When you have only a 45min, as an attendee I'd rather be interested in the
> present and may be a little bit about the future, but past is past... :)
I
ben syverson wrote:
I'm new to the list, although I've read so many of its messages I feel
like I subscribed weeks ago. :) I'm having some problems getting
libapreq2's Apache::Cookie to send out more than one cookie. The same
basic code worked fine in mp1, which makes me think I'm doing
somethi
Any additional suggestions?
I'd cite the fact that places like Google use compression for almost
all serving. A lot of people don't know that compression is wide-spread
among the big sites.
On Thu, 2005-02-03 at 16:12, Dan Brian wrote:
>
> I'd cite the fact that places like Google use compression for almost
> all serving. A lot of people don't know that compression is wide-spread
> among the big sites.
>
Yes Dan, you are right regarding the Google, however to date Google and
Yaho
I'd cite the fact that places like Google use compression for almost
all serving. A lot of people don't know that compression is
wide-spread
among the big sites.
Yes Dan, you are right regarding the Google, however to date Google and
Yahoo are rather exceptions than the rule for the content deliv
Dan Brian wrote:
I'd cite the fact that places like Google use compression for almost
all serving. A lot of people don't know that compression is wide-spread
among the big sites.
But you need to "hook" them. The fact that Google uses compression
automatically dispels the reasons people might not
On Thu, 2005-02-03 at 17:11, Dan Brian wrote:
> The fact that Google uses compression
> automatically dispels the reasons people might not find your session
> interesting: "compression is not generally compatible with most web
> browsers", "nobody is using compression", etc. My suggestion is th
I haven't personaly tried it, but I'd really be interested in knowing
how it works with mp2.
Thanks.
-Pratik
--
http://pratik.syslock.org
Problem solved.
You were quite right to ask for a test case.
In trying to create a test case I found that a module buried deep in my
application was messing up the file handle, and upgrading to a new
version of that module (OLE::Storage_Lite) solved the problem. I did
not actually figure out wha
Thank you for a good question, Pratic!
On Thu, 2005-02-03 at 17:35, Pratik wrote:
> I haven't personaly tried it, but I'd really be interested in knowing
> how it works with mp2.
>
I hope to have a good answer by the August, however I would refrain from
announcing this inside the proposal.
For
Can anyone point me to some good references on using transactions in a
mod_perl framework
My naive and possibly wrong view, is that it would be difficult to
handle transactions if DBI is recycling/sharing the connections and
making them persist
It's naive, and I'm dumb about this though.
On Feb 3, 2005, at 8:32 AM, Kurt Hansen wrote:
Have you checked the expiration of your cookies?
Hi Kurt,
I cut out the expires, domain and path information to make a more
concise listing for email. The expires is set to '+12h,' and is set
fine for the last cookie out. I haven't looked at the code
On Thu, 2005-02-03 at 14:15 -0500, Jonathan Vanasco wrote:
> Can anyone point me to some good references on using transactions in a
> mod_perl framework
http://modperlbook.com/html/ch20_01.html
> My naive and possibly wrong view, is that it would be difficult to
> handle transactions if DBI is
ben syverson <[EMAIL PROTECTED]> writes:
> I haven't looked at the code, but I suspect that "bake" is
> accidentally doing the equivalent of $r->headers_out->set('Set-Cookie'
> => $cookie) rather than $r->headers_out->add('Set-Cookie' =>
> $cookie)...
No that's not the problem. There's a bug i
On Thu, 3 Feb 2005, Stas Bekman wrote:
Almost there. What this report lacks is:
1) the explanation of how this script was invoked. Is it running under
ModPerl::Registry or else? Please show us the relevant httpd.conf bits.
2) backtrace. Please read:
http://perl.apache.org/docs/2.0/user/help/help.
[EMAIL PROTECTED] wrote:
On Thu, 3 Feb 2005, Stas Bekman wrote:
Almost there. What this report lacks is:
1) the explanation of how this script was invoked. Is it running under
ModPerl::Registry or else? Please show us the relevant httpd.conf bits.
2) backtrace. Please read:
http://perl.apache.org
On Feb 3, 2005, at 2:25 PM, Joe Schaefer wrote:
No that's not the problem. There's a bug in how 2.04 bakes
cookies (it sets the table entry using apr_table_addn on a
stack buffer instead of calling apr_table_add).
Blamo. That definitely explains it -- thanks!
It doesn't help that the libapreq2 tes
20 matches
Mail list logo
