Status of Apache 2 Port

Howdy,

I've just about finished everything I could find in getting
Bricolage  
to work on Apache 2. Today I'll merge it into trunk. After
that, there  
are just a few things I want to look at before packaging up
a  
developers release:

* Test the SOAP interface and bric_dist_mon under Apache 2.

* A few more bugs in 1.10.x. I'd like someone to package up
and  
release 1.10.5 after that. Any takers?

* Merge rev_1_10 into trunk again to get all the latest bug
fixes.

* Figure out the whole business with logging out of two
servers with  
SSL. I disabled it, as it didn't work for me on either
mod_perl 1 or  
mod_perl 2, but that was before I fixed a few other things.
It is  
weird, but it might be because, technically, the SSL and
non-SSL  
connections are different "servers", and thus
would have their own  
cookies. I think. Does that sound right?

* Check to see if switching from "SetHandler
perl-script" to  
"SetHandler modperl" got rid of that weird
subrequest.

* Merge Brian Smith's installation patches.

* Edit Bric::Changes.

* Fix a few other Ajax-related bugs I've noticed.

* Determine what happened to Devel::Profiler support. Scott,
can you  
address this?

* Upgrade Kineticode's Bricolage to trunk and using Apache
2, and  
document how users can upgrade existing Bricolage
installations to  
switch to Apache 2.

Overall, I'm quite happy with the Apache 2 support.  
Bric::App::ApacheConfig and some the installation scripts
are quite  
ugly, but the replacement of various other Apache features
with  
Bric::Util::ApacheReq, Bric::Util::ApacheUtil,
Bric::Util::Cookie, and  
HTML::Entities is truly welcome. Overall, configuration  
notwithstanding, the code is in general improved. Nice work
Chris and  
Scott, greatly appreciated!

Thanks,

David

On Thu, 24 Apr 2008, David E. Wheeler wrote:
> I've just about finished everything I could find in
getting Bricolage
> to work on Apache 2. Today I'll merge it into trunk.

And so you did. Awesome.


> * A few more bugs in 1.10.x. I'd like someone to
package up and release 
> 1.10.5 after that. Any takers?

I can do it if you want.
Though it won't be anything high-profile.


> * Determine what happened to Devel::Profiler support.
> Scott, can you address this?

I removed it in r7990 (in dev_apache2) as part of
trying to get modperl2 working [cd lib/Bric/App/ ; svn log]
:

------------------------------------------------------------
------------
r7991 | slanning | 2007-10-05 11:40:10 +0200 (Fri, 05 Oct
2007) | 24 lines
[...]
(P.S. I forgot to mention in the previous commit:
I removed Devel::Profiler support, since that hasn't
been working anyway since the Callback changes a few years
ago.)



By "the Callback changes", I mean
Params::CallbackRequest +
MasonX::Interp::WithCallbacks. Sam has obviously lost
interest
in Devel::Profiler, so maybe if someone wanted to get
another profiler working...
(This thread: http://marc.info/?l=bricolage-devel&m=10621
5281801145&w=2
I remember it because of the pain of isolating the
"using a code ref as a hash key" thing that broke
Devel::Profiler.  )

On Apr 25, 2008, at 05:20, Scott Lanning wrote:

>> * A few more bugs in 1.10.x. I'd like someone to
package up and  
>> release 1.10.5 after that. Any takers?
>
> I can do it if you want.
> Though it won't be anything high-profile.

Thanks, I appreciate it. I'll finish a couple of bugs today,
and then  
it'll be ready for you to release.

> I removed it in r7990 (in dev_apache2) as part of
> trying to get modperl2 working [cd lib/Bric/App/ ; svn
log] :
>
>
------------------------------------------------------------
------------
> r7991 | slanning | 2007-10-05 11:40:10 +0200 (Fri, 05
Oct 2007) | 24  
> lines
> [...]
> (P.S. I forgot to mention in the previous commit:
> I removed Devel::Profiler support, since that hasn't
> been working anyway since the Callback changes a few
years ago.)

I thought that it had been Devel::Profile that didn't work,
but  
Devel::Profiler did. Am I misremembering? I never used the
profiling  
stuff myself, so I'm not at all sure.

> By "the Callback changes", I mean
Params::CallbackRequest +
> MasonX::Interp::WithCallbacks. Sam has obviously lost
interest
> in Devel::Profiler, so maybe if someone wanted to get
> another profiler working...
> (This thread: http://marc.info/?l=br
icolage- 
> devel&m=106215281801145&w=2
> I remember it because of the pain of isolating the
> "using a code ref as a hash key" thing that
broke  
> Devel::Profiler.  )

Oh, so maybe it was Devel::Profile that worked and not  
Devel::Profiler? Ah well, whatever, I'm happy to leave what
hooks we  
have in there until someone decides they need it and fixes
it.

Thanks,

David

On Apr 24, 2008, at 10:42, David E. Wheeler wrote:

> * Test the SOAP interface and bric_dist_mon under
Apache 2.

Check.

> * A few more bugs in 1.10.x. I'd like someone to
package up and  
> release 1.10.5 after that. Any takers?

Check.

> * Merge rev_1_10 into trunk again to get all the latest
bug fixes.

Check.

> * Figure out the whole business with logging out of two
servers with  
> SSL. I disabled it, as it didn't work for me on either
mod_perl 1 or  
> mod_perl 2, but that was before I fixed a few other
things. It is  
> weird, but it might be because, technically, the SSL
and non-SSL  
> connections are different "servers", and thus
would have their own  
> cookies. I think. Does that sound right?

This is next.

> * Check to see if switching from "SetHandler
perl-script" to  
> "SetHandler modperl" got rid of that weird
subrequest.

Check: Yes, it did get rid of the subrequest. See

   http://www.gossamer-threads.com/lists/modperl/modperl
/97100

for all the gory details.

> * Merge Brian Smith's installation patches.

Check.

> * Edit Bric::Changes.

Check.

> * Fix a few other Ajax-related bugs I've noticed.

Next up.

> * Determine what happened to Devel::Profiler support.
Scott, can you  
> address this?

Check.

> * Upgrade Kineticode's Bricolage to trunk and using
Apache 2, and  
> document how users can upgrade existing Bricolage
installations to  
> switch to Apache 2.

After the above remaining issues are addressed, I'll do
this. Probably  
on Monday at this point.

> Overall, I'm quite happy with the Apache 2 support.  
> Bric::App::ApacheConfig and some the installation
scripts are quite  
> ugly, but the replacement of various other Apache
features with  
> Bric::Util::ApacheReq, Bric::Util::ApacheUtil,
Bric::Util::Cookie,  
> and HTML::Entities is truly welcome. Overall,
configuration  
> notwithstanding, the code is in general improved. Nice
work Chris  
> and Scott, greatly appreciated!

I'll get a dev release out on Monday. 

Best,

David

On Apr 25, 2008, at 15:50, David E. Wheeler wrote:

>> * Figure out the whole business with logging out of
two servers  
>> with SSL. I disabled it, as it didn't work for me
on either  
>> mod_perl 1 or mod_perl 2, but that was before I
fixed a few other  
>> things. It is weird, but it might be because,
technically, the SSL  
>> and non-SSL connections are different
"servers", and thus would  
>> have their own cookies. I think. Does that sound
right?
>
> This is next.

Check.

>> * Fix a few other Ajax-related bugs I've noticed.
>
> Next up.
>
>> * Upgrade Kineticode's Bricolage to trunk and using
Apache 2, and  
>> document how users can upgrade existing Bricolage
installations to  
>> switch to Apache 2.
>
> After the above remaining issues are addressed, I'll do
this.  
> Probably on Monday at this point.

Starting on these tonight, will likely finish on Monday.

Best,

David