[
https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886822#comment-13886822 ]
Ean Schuessler commented on OFBIZ-5522:
---------------------------------------
That's a rather odd graph since it unifies all the Chromes and all the Firefoxes but not the IEs. I guess its because of the feature disparities between the versions of IE. One important consideration with all of this is that websockets have quite variable availability across these browsers as well. That is probably a larger consideration than the ECMAScript issue. I think its really about identifying the browsers we want (need) to support and then building test cases to validate functionality. Personally I would throw IE7 and IE8 off the bus when it comes to designing forward. Those browsers are dead and virtually gone so letting their limitations influence the client design for the coming years doesn't make a lot of sense.
> 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)
Locked
