[
https://issues.apache.org/jira/browse/SHINDIG-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654679#action_12654679
]
Kevin Brown commented on SHINDIG-696:
-------------------------------------
I don't think that's right, though this is actually one item in the pipelining
spec that needs to be addressed. If I'm not using a proxied render, data
pipelining is still supposed to be used to satisfy preloading of social data on
the client.
Another thing in the pipelining spec that needs to be made explicit is that
os:MakeRequest is intended to completely replace the Preload element.
What we probably need is some way for developers to specify what preloaded data
goes to the client and what gets posted to their server. Of course, this is
only relevant when proxied rendering is used. I think there are three options:
- Always post everything. This is the simplest approach, since if the developer
actually wants the preloaded content in the output they can just echo it back.
- Always emit the preloaded data into the client code as well as posting.
- Add an attribute on os:* specifying how it should be used.
If the latter, we should also structure the code in such a way that we can
issue the proxied render in parallel with the preloaded items.
I don't care so much about HTTP preloads because developers probably shouldn't
be issuing http requests and then having them posted back to their own site in
any case. There's only a very small set of contrived situations where that
would have any benefit at all, and I don't think they're worth spending much
effort on.
I also don't think that Callable<Map<String, ...> is very clean. The original
point of the Map<String, Callable> was under the assumption that every request
was indnepenent, but that doesn't necessarily make sense for social data. I'd
much rather see something like:
Collection<PreloadedData>
Where PreloadedData can be modified to export single as well as multi mappings
and we could eliminate that ugly bit of template nastiness.
> 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.
