You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2014/02/01 09:30:09 UTC

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

    [ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888490#comment-13888490 ] 

Jacques Le Roux edited comment on OFBIZ-5522 at 2/1/14 8:29 AM:
----------------------------------------------------------------

Ean,

I think you are right http://youmightnotneedjquery.com


was (Author: jacques.le.roux):
Ean,

I think you are right http://youmightnotneedjquery.com/?ref=heydesigner

> Introduce websocket usage
> -------------------------
>
>                 Key: OFBIZ-5522
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5522
>             Project: OFBiz
>          Issue Type: Task
>          Components: framework
>    Affects Versions: SVN 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.1.5#6160)