Re: [Maybe OT] Modular design - calling pages like a subroutine with a twist.

Perrin Harkins writes: > breaks caused by the request model of HTTP, and that's what I was commenting > on. You're talking about a way to preserve data across multiple page > requests. FormContext maintains an "HTTP call stack", which holds the parameters (form, query, path_info) and return addr

Re: [Maybe OT] Modular design - calling pages like a subroutine with a twist.

> > In my opinion, trying to abstract that stuff away in a web application > > causes to more problems than it solves, especially where back buttons and > > bookmarks are concerned. > > We haven't found this to be the case. Our servers are sessionless, > so bookmarks work fine. These are differe

Re: [Maybe OT] Modular design - calling pages like a subroutine with a twist.

> In my opinion, trying to abstract that stuff away in a web application > causes to more problems than it solves, especially where back buttons and > bookmarks are concerned. We haven't found this to be the case. Our servers are sessionless, so bookmarks work fine. Back buttons aren't any mor

Re: [Maybe OT] Modular design - calling pages like a subroutine with a twist.

On 15 Nov 2001, at 15:33, Perrin Harkins wrote: > The original e-mail was confusing, but I think what he's after is not so > much the ability to call pages as subs but rather the ability to abstract > away the fact that a sub might actually involve multiple user interactions > (present a form,

Re: [Maybe OT] Modular design - calling pages like a subroutine with a twist.

> I'll try to show how Apache::ASP could help here. In Apache::ASP, > scripts can be executed as subroutines, even with return values, > and I think this goes to the heart of what you need here. The original e-mail was confusing, but I think what he's after is not so much the ability to call pag

Re: [Maybe OT] Modular design - calling pages like a subroutine with a twist.

Scott Chapman wrote: > > I'm very interested in making a modular site design but haven't > found the tools yet to allow this with the twist I'm looking for. > I'll try to show how Apache::ASP could help here. In Apache::ASP, scripts can be executed as subroutines, even with return values, and

Re: [Maybe OT] Modular design - calling pages like a subroutine with a twist.

At 08:42 15.11.01 -0800, you wrote: >Say I have a page that encapsulates some functionality, such as >sending a form then validating the contents that are returned. I'd >call that PageB. > >PageB could be more than one page or a page calling itself, etc. > >When PageA calls PageB, as soon as PageB

Re: [Maybe OT] Modular design - calling pages like a subroutine with a twist.

> When PageA calls PageB, as soon as PageB finishes presenting > the form it doesn't stop but drops out the bottom and returns > immediately to PageA. In bOP we use "FormContext" to solve this problem. PageB requires context and bOP knows how to return to

Re: [Maybe OT] Modular design - calling pages like a subroutine with a twist.

Original Message - From: "Scott Chapman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 15, 2001 11:42 Subject: [Maybe OT] Modular design - calling pages like a subroutine with a twist. > I'm very interested in making a modular site des

[Maybe OT] Modular design - calling pages like a subroutine with a twist.

I'm very interested in making a modular site design but haven't found the tools yet to allow this with the twist I'm looking for. Say I have a page that encapsulates some functionality, such as sending a form then validating the contents that are returned. I'd call that PageB. PageB could be