<br><br><div class="gmail_quote">On Tue, Aug 4, 2009 at 1:08 AM, Mike Wilson <span dir="ltr"><<a href="mailto:mikewse@hotmail.com">mikewse@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Michael Nordman wrote:<br>
<div class="im">> On Mon, Aug 3, 2009 at 2:37 PM, Mike Wilson wrote:<br>
> > Btw, another reflection is that this mail thread is about<br>
> > introducing a client/server model in the browser. Some<br>
> > mentions of complex code in the background page, f ex building<br>
> > the HTML for the visible window, make me think of traditional<br>
> > server-centric webapps, but inside the browser. I've made<br>
> > the below table to illustrate this, and I mean to point out<br>
> > similarities between traditional server-centric and the new<br>
> > background_page-centric webapps, and between client-centric<br>
> > and visible-centric webapps. Maybe this can inspire some new<br>
> > thoughts.<br>
><br>
> Yes... client/server model in the browser... good observation... and a<br>
> good way to think about the direction I would like to see things go.<br>
> Incidentally, that line of thinking is my motivation for the<br>
> introduction of script-generated responses in this (HTML5) system<br>
> design.<br>
<br>
</div>Ah, I seem to have missed that. Makes total sense for offline<br>
as it probably makes it a lot easier to port server-centric<br>
apps to the cache, and well, there is already a concept of<br>
serving files (although only static).<br>
<br>
It's not a small thing to add, but if this is taken further I<br>
think coordination should be done with current inititatives<br>
using JS in server-side web platform designs, such as:<br>
ServerJS WSGI <a href="https://wiki.mozilla.org/ServerJS/WSGI" target="_blank">https://wiki.mozilla.org/ServerJS/WSGI</a><br>
(several products pointed to by comparison table)<br>
Joyent Smart <a href="http://becoming.smart.joyent.com/index.html" target="_blank">http://becoming.smart.joyent.com/index.html</a><br>
+ other stuff using EnvJS, etc...<br>
<br>
This would make it easier to move code between server and<br>
client, simplifying creation of distributed and offline apps.</blockquote><div><br></div><div>Exactly! (and thnx for the pointers)</div><div><br></div></div>