[Templates] using frames?

[Kirk]

got it, thanks...dropping the frames as i type.  and thank you for the
explanation.

kirk


>-----Original Message-----
>From: Mark Mills [mailto:mark@xodiax.com]
>Sent: Wednesday, September 04, 2002 12:56 PM
>To: thedog@scriptdoggie.com; Templates
>Subject: RE: [Templates] using frames?
>
>
>> -----Original Message-----
>> From: Kirk [mailto:thedog@scriptdoggie.com]
>> Subject: RE: [Templates] using frames?
>>
>> and if i want to process the included file within the
>> frameset?  what then?
>
>Well, you're going to be sorely disappointed. Apache::Template
>doesn't offer that functionality. Neither is there any easy way
>in any other Template handler do deal with your "issue".
>
>No one has written what you want because it is technically
>infeasable. I don't think "Frames" work like you think they
>work. It is a total hack around a stateless system.
>
>Your browser comes to the site, requests the frame page, and
>gets it back. It then notices that it is a frame document,
>and splits the screen up like the document asks, then goes out
>and requests the individual pages to put in those screen areas.
>
>If your template caused the other pages to be written, then
>that user's browser would come get them. BUT, if two users
>request the frame page at the same time, both will likely wind
>up with one of their sets of sub-pages. The webserver can't
>keep it straight since it has no user-tied-state. And you can't
>template pages and then wait for only the right user to come get
>them without massive hackery.
>
>The solution, which is ugly, is to pass state within the URLs
>and let the secondary pages template themselves based on their
>GET arguments.
>
>Honestly, I'd recommend you drop the frames and template
>everything in one page. It seems like more work per request
>(and it is) but you simplify the design and up the security.
>
>--mark mills
>