[
http://jira.amdatu.org/jira/browse/AMDATU-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10293#comment-10293
]
Ivo Ladage - van Doorn commented on AMDATU-82:
----------------------------------------------
I'm a bit lost here. The issue is network latency, the fact that upon opening
the dashboard, adding gadgets and viewing available gadgets takes a long time
since each gadgetspec needs to be retrieved over the network again and again
and you never know response times of each container that provides the gadget,
if it implements http caching or even (ever) returns a response at all.
It would be nice if all opensocial container hosting the gadgets follow the
rules as described in Angelo's link and it would be nice if all servers in the
world would have SSDs, that would speed up the social apps but it wouldn't
resolve this issue.
The issue is that our gadgetstore holds URLs to maybe hundreds of gadgets,
served by many different opensocial containers. Right now, our store holds only
15 URLs and we are already facing a performance issue (hence this issue). The
gadgetspec of each gadget needs to be retrieved from the opensocial container
that hosts the gadget. We do not have any influence on how http caching is
implemented by the container providing this gadgetspec. Shindig too does cache
the gadgetspecs locally in a configurable cache, since there is an obvious need
for it. Do you really want to depend your own response times by design on
response times and http caching headers of each container hosting a gadget
available in your store (which can be added by any user)?
The best we could do is to mimic the browser cache in our own cache,
considering the http cache headers send by the several opensocial containers
out there. We could use some http client cache library for that. Obviously,
this simple caching mechanism could be improved in many ways. But my goal
fixing this issue was to come up with a simple caching mechanism, which is
exactly what it is.
> Loading of gadget definitions is very slow
> ------------------------------------------
>
> Key: AMDATU-82
> URL: http://jira.amdatu.org/jira/browse/AMDATU-82
> Project: Amdatu
> Issue Type: Bug
> Components: Amdatu OpenSocial
> Affects Versions: 0.0.4
> Reporter: Dion Meijer
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.0.6
>
>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
