>Adding AJAX to the mix ruins that. Even if you are a programmingIt seems that AJAX is necessary not from a technical perpective but a user
>wizard, and I immodestly count myself in that group, AJAX makes things
>freakin' complicated. You are now deeply involved in client/server
>programming, with complicated inter-process communication. (Yes,
>technically a CGI script is part of a client/server communication, but
>that's all hidden from me.) State is split between the server and the
>client in ways that are not yet standardized and somewhat difficult to
perspective. On web applications that have a lot of functionality and client
server communication page refreshes seem obsolete. My current app basically
has two pages a public page and a password protected page. The protected
page has many "contexts", ie instread of redirecting to another page, i use
same page. So there is no redirect or refresh just different content loading
I agree with you that maintaining state on the client and the server is a
However, yesterday I had the idea that a cookie seems like a good way to
On Wed, Sep 10, 2008 at 2:49 AM, Arnar Birgisson <arna...@gmail.com> wrote:--
> Hi Gloria,
> On Tue, Sep 9, 2008 at 23:10, Gloria W <strang...@comcast.net> wrote:
> ProtocolBuffers are not meant to replace JSON, they are just an
> If browser start supporting ProtocolBuffers natively and provide the
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.