On Thu, 13 Jul 2000, Honza Pazdziora wrote:
> On Thu, Jul 13, 2000 at 01:54:28PM -0700, Andrew Chen wrote:
> >
> > That sounds like a pretty concrete solution. It seemed weird that there
> > wasn't an in-between solution to the issue.
>
> The reason probably is, that you really want to clean your code at
> the end. So all the big guys are either writing everything using
> Apache::Request, or cleaned up their *.pl's to run fine within
> Apache::Registry. You need such hackery only for the migration part,
> not for production code.
Yes, ultiimately we are looking to do that. Between the time that it takes
for us to set this up and for people to realize how much of a speed boost
there is (and thus dedicate resources to it) we need to come up with an
interim solution. Thus this these two hacky solutions have been thought
up. If you have any other ideas in terms of what another solution for the
migration should be, I'd love to hear it.
So from your first e-mail, I guess the idea of a module that would be
loaded at the end up the startup file that stores away all the information
up to that point so that the rest of the stuff loaded after then is
flushed-- you've never heard of anything that does something like that?
Thanks,
Andrew
