Hi All,

Following requirement is received from Analytics and IoT teams.

Users - Dashboard designers

Description - The users should be able to iframe the gadgets into another
page or webapp. Further the user could define the pages, layout and render
the gadgets, and there could be a pub-sub configuration between the
gadgets. And it's required to iframe such designed gadgets into another app
and provide the same level of functionality.

Benefits - The platform capabilities are not bound within DS only, and
could be used in other servers as well.

Acceptance Criteria -

1. Should be able to iframe gadgets with it's settings into another
page/webapp

2. Should be able to iframe the pub-sub gadgets of a page, into another
page/webapp.

In the current implementation of DS server, the gadget rendering happens as
follow in a high level view,

With this we cannot directly get the iframe url generated by shindig server
to embed the gadget in the another location because that URL will not
properly render all the functionalities related to that gadget when it is
used outside the DS.

So in order to solve this issue, we came up with following solution.

We decided to give a separate URL for each gadgets using their gadget id
and dashboard id and then we can use that URL to embed the gadgets in
different web pages. But when we take the inter-gadget communication
mechanism in DS server, it is done by pub-sub model. Wiring between
publisher and subscriber happens through the parent container. But when we
ship gadgets separately using unique URLs, we cannot achieve the
inter-communication between gadgets through the above mentioned mechanism.

So in order to solve this issue, we need to use the dashboard server as the
mediation point between publisher and subscriber. In order to communicate
with the server we need to use the web sockets. But if we use the web
sockets, whenever a publisher publish events, it will be notified to all
the subscribers since websockets cannot differentiate between different
subscribers.

Currently we are in the process of investigating other alternatives to
satisfy these requirements. Any ideas and comments on this is highly
appreciated.

Thanks.

Regards,
Megala

-- 
Megala Uthayakumar

Software Engineer
Mobile : 0779967122
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to