Ian Hickson wrote:
I looked at this but could not immediately work out how to leverage this
idea in the context of HTML5, unfortunately. Do you know if any work is
being done on POEs still?
I'd be surprised if Mark (the author) didn't want to move forward with
it. There are some related
On Thu, 21 Apr 2005, Kornel Lesinski wrote:
On Thu, 21 Apr 2005 14:07:45 +0100, Ian Hickson [EMAIL PROTECTED] wrote:
Anyone have any concrete proposals? :-)
Persistent associative array that stores anything*, just like session
object in PHP and ASP.
This might be called:
On Thu, 21 Apr 2005, Olav Junker Kjær wrote:
Anyone have any concrete proposals? :-)
How about a javascript structure which may be arbitrary deep, but only
may contain javascript built-in types (Object, Array, string, number,
bool, Date etc.)? This would be very easy to use, although
On Thu, 21 Apr 2005, Robert Sayre wrote:
Olav Junker Kjær wrote:
Ian Hickson wrote:
Anyone have any concrete proposals? :-)
http://www.crockford.com/JSON/index.html ?
It turns out that the way I ended up defining this, I didn't need to
describe the back-end serialisation format.
Ian Hickson wrote:
I used this idea for the window.history.pushState() idea:
http://whatwg.org/specs/web-apps/current-work/#the-session
Let me know if you have any comments.
It doesn't cover the bookmark case, only the back-forward case, so I don't
think this removes the need for a
On Thu, 21 Apr 2005, Brad Neuberg wrote:
Something along these lines that would be useful is control over what
goes into the history (and what affects the back button) and what
_doesn't_. Alot of times I shoot off RPC type functions using
XmlHttpRequest that I _dont_ want in the history,
On Fri, 22 Apr 2005, Dimitri Glazkov wrote:
Maybe it would a better idea to introduce functionality that
standardizes a usability-perfect simulation of a request within the same
page? I think that is what Brad is writing about.
In other words, instead of trying to come up with a vehicle
Flash MX has a scriptable object named SharedObject that can contain far
more application state than a normal cookie can, but for Flash
movies. Perhaps this is a good concept to steal from Flash? They've
thought through the API pretty well. One thing that is unique about these
is that they
IMHO, one of the biggest obstacles for growth in Web applications
development is the fact that the entire application lives in the scope
of one request.
Once next request is made, the browser essentially forgets
everything and the whole new cycle of loading, initialization, and
binding begins.
