You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "F. Da Costa Gomez" <dc...@fixed.com> on 2003/06/07 14:40:34 UTC
Frames or Table structure
Hi,
Without wanting to go into the pros and cons of frames vs tables
(obviously there is a difference for otherwise they would not BOTH
exist!) I would like to post a Q re. the use of either one with Tapestry.
I'm at a crossroads here, wanting to start on a foundation for my app I
was wondering whether a frame structure or table structure (startscreen/
visual work-environment) would be more appropriate. Basically I can do
both so it comes down to this Q:
On a heavy load site (500+ *working* users) which structure gives the
smallest hit on the server. I don't mind using the client for stuff
(cheap processingpower) but I would like to relieve the server as much
as I can. My gut tells me that less rendering (read frames) means more
users can work simultaneously. Granted however that u Tapestry gut is
still quite undeveloped.
Any input would be greatly appreciated.
TIA
Fermin DCG
Re: Frames or Table structure
Posted by "F. Da Costa Gomez" <dc...@fixed.com>.
Hmm, seems to me y'r suggesting *not* 2 use frames. ;-)
Thx 4 the unambiguous answer,
Cheers,
Fermin DCG
Howard M. Lewis Ship wrote:
>Avoid frames. Modern browsers support absolute positioning using CSS, so there's nothing you can't
>accomplish using standard web pages.
>
>Anytime you start using frames, you start requiring multple server round trips for each user action.
>
>You end up having to write lots of JavaScript to coordinate updates to frames.
>
>Bookmarks don't work properly anymore.
>
>Browser-back buttons become worse.
>
>Just avoid frames. They are *so* nineties.
>
>--
>Howard M. Lewis Ship
>Creator, Tapestry: Java Web Components
>http://jakarta.apache.org/tapestry
>
>
>
>
>
>>-----Original Message-----
>>From: F. Da Costa Gomez [mailto:dcg@fixed.com]
>>Sent: Saturday, June 07, 2003 8:41 AM
>>To: Tapestry users
>>Subject: Frames or Table structure
>>
>>
>>Hi,
>>
>>Without wanting to go into the pros and cons of frames vs tables
>>(obviously there is a difference for otherwise they would not BOTH
>>exist!) I would like to post a Q re. the use of either one
>>with Tapestry.
>>
>>I'm at a crossroads here, wanting to start on a foundation
>>for my app I
>>was wondering whether a frame structure or table structure
>>(startscreen/
>>visual work-environment) would be more appropriate. Basically
>>I can do
>>both so it comes down to this Q:
>>On a heavy load site (500+ *working* users) which structure gives the
>>smallest hit on the server. I don't mind using the client for stuff
>>(cheap processingpower) but I would like to relieve the
>>server as much
>>as I can. My gut tells me that less rendering (read frames)
>>means more
>>users can work simultaneously. Granted however that u Tapestry gut is
>>still quite undeveloped.
>>
>>Any input would be greatly appreciated.
>>
>>TIA
>>Fermin DCG
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
>
>
>
RE: Frames or Table structure
Posted by "Howard M. Lewis Ship" <hl...@attbi.com>.
Avoid frames. Modern browsers support absolute positioning using CSS, so there's nothing you can't
accomplish using standard web pages.
Anytime you start using frames, you start requiring multple server round trips for each user action.
You end up having to write lots of JavaScript to coordinate updates to frames.
Bookmarks don't work properly anymore.
Browser-back buttons become worse.
Just avoid frames. They are *so* nineties.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
> -----Original Message-----
> From: F. Da Costa Gomez [mailto:dcg@fixed.com]
> Sent: Saturday, June 07, 2003 8:41 AM
> To: Tapestry users
> Subject: Frames or Table structure
>
>
> Hi,
>
> Without wanting to go into the pros and cons of frames vs tables
> (obviously there is a difference for otherwise they would not BOTH
> exist!) I would like to post a Q re. the use of either one
> with Tapestry.
>
> I'm at a crossroads here, wanting to start on a foundation
> for my app I
> was wondering whether a frame structure or table structure
> (startscreen/
> visual work-environment) would be more appropriate. Basically
> I can do
> both so it comes down to this Q:
> On a heavy load site (500+ *working* users) which structure gives the
> smallest hit on the server. I don't mind using the client for stuff
> (cheap processingpower) but I would like to relieve the
> server as much
> as I can. My gut tells me that less rendering (read frames)
> means more
> users can work simultaneously. Granted however that u Tapestry gut is
> still quite undeveloped.
>
> Any input would be greatly appreciated.
>
> TIA
> Fermin DCG
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>