1 / 7

PVSS Web Client PVSS Pocket Client

PVSS Web Client PVSS Pocket Client. Daniel.Rodrigues@cern.ch. Web Solutions for PVSS Customers were asking for solutions integrating Web and PVSS Integration with modern browsers Easy to use on different platforms Better Scaling Use of Open Protocols Because so…

lrenfrow
Download Presentation

PVSS Web Client PVSS Pocket Client

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PVSS Web ClientPVSS Pocket Client Daniel.Rodrigues@cern.ch

  2. Web Solutions for PVSS • Customers were asking for solutions integrating Web and PVSS • Integration with modern browsers • Easy to use on different platforms • Better Scaling • Use of Open Protocols • Because so… • ETM is developing two different solutions • Web Client • Pocket Client • Available on PVSS 3.9, currently being tested at CERN Openlab PVSS Web, FWWG, November 2010

  3. Web Client • Web Client • Is a Plugin, to be installed at the end browser • Supports all CERN platforms (Lin/Win, IE/Firefox) • PROS • - Easy to install • Project files downloaded on the fly (including EWO’s and CtrlExtensions) • Behaves like any Remote UI (no new development required) • Proxy forwarding implemented • CONS • - Install admin rights • Upper limits in Performance • Some limitations (no RDBQueryDirect, ActiveX, extensions dependencies) • Authentication limited • Cache conflicts PVSS Web, FWWG, November 2010

  4. Web Client • Interesting features: • cacheTimeoutSecs : if a new file is necessary, checks if it already exists, otherwise downloads from the server  [Automatic Project Update] • the only HTTP traffic is for connection and file download. PVSS messages use a spawn process (PVSStoolTunnel) • the para module can be open from the web client PVSS Web, FWWG, November 2010

  5. Web Client • Comment on cons: • RDBQueryDirect. • wherever the browser would open, oracle client would be necessary. • even though, requests are honoured, albeit eventual reducing performance. • Ewo’s and Ctrl Extensions using external libraries might not be available on client • Will use the available dynamic loader! • Performance was greatly improved from the extensive testing done last year • First smoke tests, up to ~600 Hz on dpConnect changes in 5 simultaneous clients for 1kHz on the server. • Firewall issues might remain. Proxying works on my test machines, but CERN setup could prove yet a challenge • Let’s see it working? Please point your laptops to http://pcen33050.cern.ch PVSS Web, FWWG, November 2010

  6. Pocket Client • Pocket Client • Converts panels into HTML and Java Script • Pros • No need to install a plugin • Any web browser supporting Javascript should support the Pocket Client • It is a “real” Web Solution. • Cons • Right now, only works with the panel topology • Only Standard Object Library objects are convertible right away • No Ctrl code is converted (need to implement in html and Javascript for each panel) • Browser must support SVG or VML • Look and feel might change from browser to browser • No dollar parameters • No redundancy • Only last values are sent to clients, meaning all values in below a blocking time PVSS Web, FWWG, November 2010

  7. Pocket Client PVSS Web, FWWG, November 2010

More Related