NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Thin Client has been implemented in the NWS version of AWIPS2 since version 11.x for both Linux and Windows builds. It's described in Chapter 14 of the AUM and Chapter 26 of the Combined SMM. Like most network programs, AWIPS2 performance depends on both latency and throughput of the link and so Thin Client mode attempts to optimize these albeit at the cost of some loss of functionality. In addition, AWIPS2 was designed to be have all configuration data centrally controlled and dynamically updated but this means a lot of round-trip client-server transactions for every action. The java serialization of these transactions was also optimized for flexibility and not size/speed. * The "Localization Caching" and "Map Caching" options disable checking for new versions of this data and uses what's local. You may even pre-load all localization data to the client which will speed CAVE startup considerably over a slow link. * Product data caching becomes more aggressive at the cost that partially populated products may not be updated when complete. * You can define a proxy server so both EDEX and Pypies use a single external port (e.g. port 80 or port 443.) If you set this up as described, all communications to/from the server will also utilize gzip compression (really helps with some transactions, not so much for satellite images.) * You can turn off the JMS push notification of new data and replace it with timed updates. Last I checked, Thin Client mode required AlertViz and CAVE to be started separately (and with their respective '-component thin..." argument.) -- Erik ________________________________________ From: awips2-users-bounces@xxxxxxxxxxxxxxxx [awips2-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Brendon Hoch [bhoch@xxxxxxxxxxxx] Sent: Friday, December 11, 2015 11:38 AM To: Neil Smith; awips2-users@xxxxxxxxxxxxxxxx Subject: Re: [awips2-users] Teaching in a Computer Lab Environment? [...] I had read that NOAA and Unidata were separately working on developing a AWIPS 2 Thin Client which would run under Windows and use remote servers, but haven't seen any recent news regarding their efforts. The information contained in this email message is intended only for the use of the individual(s) to whom it is addressed and may contain information that is privileged and sensitive. If you are not the intended recipient, or otherwise have received this communication in error, please notify the sender immediately by email at the above referenced address and note that any further dissemination, distribution or copying of this communication is strictly prohibited. The U.S. Export Control Laws regulate the export and re-export of technology originating in the United States. This includes the electronic transmission of information and software to foreign countries and to certain foreign nationals. Recipient agrees to abide by these laws and their regulations -- including the U.S. Department of Commerce Export Administration Regulations and the U.S. Department of State International Traffic in Arms Regulations -- and not to transfer, by electronic transmission or otherwise, any content derived from this email to either a foreign national or a foreign destination in violation of such laws.
awips2-users archives: