Client side Data Pipelining in OS Templates

[le...@google.com]

Reviewers: shindig-dev,

Description:
Overhauled the implementation of Data Pipelining in Templates.
   <os:ViewerRequest>, <os:OwnerRequest>, <os:PeopleRequest> (@userId and
@groupId only for now) and <os:DataRequest> (@href and @format=json|text
only for now).
   Supports automatic dependency detection and chaining

TODOs:
   * support all proposed tags, attributes
   * remove dependency on templates
   * move into own feature, or core.
   * add more Unit tests

Please review this at http://codereview.appspot.com/10041

Affected files:
   features/opensocial-templates
   features/opensocial-templates/base.js
   features/opensocial-templates/compiler.js
   features/opensocial-templates/container.js
   features/opensocial-templates/data.js
   features/opensocial-templates/data_test.js
   features/opensocial-templates/ost_test.html
   features/opensocial-templates/template_test.js
   java/server/src/test/resources/endtoend/opensocial-templates/data_test.js

Re: Client side Data Pipelining in OS Templates

["Henning P. Schmiedehausen" <he...@schmiedehausen.org>]

levik@google.com writes:

>Please review this at http://codereview.appspot.com/10041

Can you please put this information into a JIRA, so that it gets tracked.  Thanks

    Ciao
        Henning

-- 
Henning P. Schmiedehausen - Palo Alto, California, U.S.A.
henning@schmiedehausen.org "We're Germans and we use Unix. 
henning@apache.org          That's a combination of two demographic groups
                            known to have no sense of humour whatsoever."
                               -- Hanno Mueller, de.comp.os.unix.programming