W3C home > Mailing lists > Public > www-talk@w3.org > May to June 2000

Re: Frames

From: Grahame Grieve <grahame@kestral.com.au>
Date: Wed, 03 May 2000 08:28:11 +1000
Message-Id: <4.1.20000503082617.00aeb1c0@10.252.1.60>
To: www-talk@w3c.org
well, this can punish the band-width, since what was being stored
was java and javascript stuff.

However this would be a bit fragile. It would be nice to have
persistent local storage on the browser as part of the standard


Grahame




At 04:49 PM 02/05/2000 -0500, you wrote:
>[Jay Chalfant <jchalfan@outbackinc.com>]
>> There is another feature of frames that is even more important from our
>> perspective. A web application may use a frameset that keeps one of the
>> frames loaded throughout the application session. This "constant" frame is
>> the only place to store persistent Java and JavaScript components. These
>> components are then used by other frames in the frameset that change as the
>> user navigates through the application. 
>> 
>> The ability to store complex state on the client in a convenient and
>> seamless fashion is a cornerstone of our approach to building web
>> applications. I'd hate to see this go away.
>
>Instead of playing tricks with the browser, why not use some http-builtin
>state management mechanism, like cookiees and then use a back end for
>persistence?
>
>-- 
>Ari							there is no spoon
>-------------------------------------------------------------------------
>http://www.nebcorp.com/~regs/pgp for PGP public key
>
Received on Tuesday, 2 May 2000 18:16:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:24 GMT