Use case: Dashboard/ticker view that can rotate information messages from various RSS sources;
In order to implement this we need to implement a data connection and feed proxy and make this available to the widgets codes as part of the choreographer API. Today widget modules are responsible for loading and managing the information - they directly interact with Web content. This can be done today via using Google AJAX RSS feed API or the widget component can make a call using XHR. The new proposal is to have a proxy component in the middle which is responsible for loading RSS information, maintaining a data store and events coordination system so that widgets can receive nodes of information. With this approach a widget should be able to collect feed items from various pre-registered feed channels thus the effect of a rotating RSS ticker for various RSS data-sources will be possible.
Use case: Dashboard/ticker view that can rotate information messages from various RSS sources;
In order to implement this we need to implement a data connection and feed proxy and make this available to the widgets codes as part of the choreographer API. Today widget modules are responsible for loading and managing the information - they directly interact with Web content. This can be done today via using Google AJAX RSS feed API or the widget component can make a call using XHR. The new proposal is to have a proxy component in the middle which is responsible for loading RSS information, maintaining a data store and events coordination system so that widgets can receive nodes of information. With this approach a widget should be able to collect feed items from various pre-registered feed channels thus the effect of a rotating RSS ticker for various RSS data-sources will be possible.