launchpad-dev team mailing list archive

[Aaron Bentley <aaron@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12-02-20 11:55 PM, Robert Collins wrote:
> So, going back at least 18 months, maybe more, there has been a
> long slow-running conversation amongst us about what we render
> were, with different projects choosing different answers.
> 
> I think we have enough data now, that we can consolidate on a good 
> default answer and ask that everyone pick that answers *by
> default* with variation needing to be experiments - explicit
> decisions to learn something new.
> 
> tl;dr: lets: * render searchable content on server side and client
> side using a common template language * render the forms needed to
> file a bug server side and optionally client side * render all
> other forms exclusively client side and have them communicate
> exclusively via the API

I think that this approach makes sense.  The current API is not
roundtrip-efficient for multiple-item listings, but forms are usually
related to a small number of items, so this should not be a problem.

You didn't specify that the API must be used when rendering searchable
content on the client side.  The JSONCache is roundtrip-efficient for
this purpose, and can also deliver identical data to client-side and
server-side templates, so I think we should prefer it for now.

If we want to use the API for client-side rendering of things like bug
and branch listings, I think we will need to change the API to make it
roundtrip-efficient, and find a way to ensure that identical data is
presented to client-side and server-side renderers.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9DzacACgkQ0F+nu1YWqI01IQCfUMoSD418g1z+ZYcno2gczYDw
dGkAnj7KwsKfJdxk9gZxmcLDBHTwpkme
=nXUt
-----END PGP SIGNATURE-----