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

Jacques Le Roux updated OFBIZ-5522:
-----------------------------------
    Comment: was deleted

(was: Consequently, you should keep in thoughts the items tend to be relocated 
according to his or her desperation. 
Also you can provide a get in touch with up to be able to a wide range of the 
shifting companies and also understand their particular strategy to going the 
different items.
Packers and Movers Mumbai or http://www.expert5th.in/packers-and-movers-mumbai/
Packers and Movers Hyderabad or 
http://www.expert5th.in/packers-and-movers-hyderabad/
Packers and Movers Pune or http://packersmoverspune.top3rd.in/
Packers and Movers Bangalore or 
http://www.expert5th.in/packers-and-movers-bangalore/
Packers and Movers Delhi or http://www.expert5th.in/packers-and-movers-delhi/
Packers and Movers Chennai @ http://www.expert5th.in/packers-and-movers-chennai/
Packers and Movers Gurgaon or 
http://www.expert5th.in/packers-and-movers-gurgaon/)

> 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)

Reply via email to