You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Akash Singh (JIRA)" <ji...@apache.org> on 2015/06/25 11:22:05 UTC

[jira] [Issue Comment Deleted] (OFBIZ-5522) Introduce websocket usage

     [ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Akash Singh updated OFBIZ-5522:
-------------------------------
    Comment: was deleted

(was: 
Thanks for sharing your info. I really appreciate your efforts and I will be waiting for your further write
<a href="http://www.smart5th.in/packers-and-movers-hyderabad/">Packers and Movers Hyderabad</a>
<a href="http://www.smart5th.in/packers-and-movers-bangalore/">Packers and Movers Bangalore</a>
<a href="http://www.smart5th.in/packers-and-movers-pune/">Packers and Movers Pune</a>
)

> Introduce websocket usage
> -------------------------
>
>                 Key: OFBIZ-5522
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5522
>             Project: OFBiz
>          Issue Type: Task
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Priority: Minor
>
> After a discussion with Ean, was suggested (draft here):
> You need a service that lets you "subscribe" a widget to an entity and
> then propagate change events to the widget as the entity is modified.
> A generic mechanism like that could eventually expand to be a general
> purpose "data bound widgets" system that mostly looks like the existing
> system but magically reflects updates.
> Could be used with/for
> * The entity cache and webforms to automatically update views when data changes. 
> * Replaces the current system notes
> * Create a dashboard type pages  (to be discussed futher)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)