[
https://issues.apache.org/jira/browse/SHINDIG-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654841#action_12654841
]
Adam Winer commented on SHINDIG-696:
------------------------------------
I don't like Callable<Map<String, .> either, especially since its worse than
that: Collection<Callable<Map<String, ...>>. I'll look into cleaning that up.
(BTW, http://codereview.appspot.com/8648 would be a great spot for these
comments.)
With regard to the first half, I've raised this as an issue on the spec group,
where the discussion belongs. I agree that data pipelining should be used to
satisfy preloading of social data on the client, but don't think that the batch
of preloaded content POSTed for proxied rendering is the right batch. Let's
continue this on the spec group.
> Data pipelining support for proxied gadget renders
> --------------------------------------------------
>
> Key: SHINDIG-696
> URL: https://issues.apache.org/jira/browse/SHINDIG-696
> Project: Shindig
> Issue Type: New Feature
> Components: Gadget Rendering Server (Java)
> Reporter: Adam Winer
> Attachments: pipelining-2.patch, pipelining-3.patch,
> pipelining-4.patch
>
>
> Add support for <os:PeopleRequest>, etc., as elements inside <Content
> type="html" href="...">, as per the data pipelining proposed specification.
> Code being reviewed at http://codereview.appspot.com/8648/publish, and to be
> uploaded here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
