launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #09068
Re: server side rendering, client side rendering, forms, oh my.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12-02-21 06:11 PM, Robert Collins wrote:
> On Wed, Feb 22, 2012 at 12:04 PM, Aaron Bentley
> <aaron@xxxxxxxxxxxxx> wrote:
>
>> But it only doubles the page size when we use server-side
>> rendering. Clients can get the JSONCache via ++model++ urls.
>
> indeed, but if they are going to request it separately, there
> isn't a functional difference vs the API (subject to making good
> API calls that fit the problem space :)) - or am I missing
> something?
The JSONCache is meant to be page-specific. I think there's a risk
that if we use the API in place of it, we'll wind up with a bunch of
page-specific API methods that aren't useful to other clients.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9HlZQACgkQ0F+nu1YWqI2niACghVIS6CnUkn+9+F45JiLkbW+y
6zkAn0HE+AmehGPaH0ZKhRcBufm1BxHl
=Bthk
-----END PGP SIGNATURE-----
References
-
server side rendering, client side rendering, forms, oh my.
From: Robert Collins, 2012-02-21
-
Re: server side rendering, client side rendering, forms, oh my.
From: Aaron Bentley, 2012-02-21
-
Re: server side rendering, client side rendering, forms, oh my.
From: Robert Collins, 2012-02-21
-
Re: server side rendering, client side rendering, forms, oh my.
From: Aaron Bentley, 2012-02-21
-
Re: server side rendering, client side rendering, forms, oh my.
From: Robert Collins, 2012-02-21