Changes between Version 33 and Version 34 of Clients


Ignore:
Timestamp:
Dec 7, 2017, 10:10:42 AM (6 years ago)
Author:
Peter Baumann
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Clients

    v33 v34  
    7979svn checkout  svn://svn.code.sf.net/p/ctsciencegtwys/mobile/trunk/iOS/EarthServer-SG-Mobile EarthServer-SG-Mobile
    8080}}}
     81
     82The following settings in the `etc/` config files should be individualized:
     83{{{
    8184# RASBASE login
    8285rasuser=rasdaman
    … …  
    9497}}}
    9598
    96 Note that passwords etc. need to be adjusted to the actual installation values.
    97 
    9899
    99100=== raswct (rasdaman Web Client Toolkit) ===
    100101
    101102This JavaScript library allows, by way of input and output widgets, to easily compose a Web client. Simple versions need only HTML, but advanced interfaces can be created. One example for the use of raswct is [http://standards.rasdaman.org standards.rasdaman.org]. See [wiki:raswct/guide documentation] for details.
    102 
    103 === rview (deprecated) ===
    104 rview is a deprecated desktop visualization client of rasdaman. It is deprecated as it uses an insecure, soon-to-be-replaced client/server protocol based on RPCs. For building clients use [http://rasdaman.org/wiki/Clients one of the Web client or the raswct library] instead.
    105 
    106 Caveat: This client is fixed to RPC as client/server protocol, hence (i) rpcbind/portmapper must be installed and running and (ii) at least one rasdaman server process using RPC must be up and running; see the rasdaman Installation Guide for details on this.
    107 
    108 Background: rview is deprecated and unmaintained. Reason is that the wxWindows library has changed so substantially that, despite severe ettempts, it was not possible to adapt the rview code; therefore, only the old binary remains available. In fact, there are strong reasons not to use rview: As highlighted, RPC is '''highly insecure''' and not recommended. Further, RPC communication is deprecated and will soon be replaced (together with HTTP and RNP) by rasnet.
    109 
    110 If you have read the above and still wish to use rview, proceed as follows: start the rpcbind service has to be started in insecure mode (or rasdaman has to be started as root, which is strongly discouraged as well) in order for rview to be able to connect to rasdaman.
    111 
    112 To start rpcbind in insecure mode, edit /etc/init.d/rpcbind (more recently: /etc/init/portmap.conf) and add '-i' to the OPTIONS variable. Start rpcbind. Restart rasdaman. Open rview with
    113 {{{
    114 #!sh
    115 cd $RMANHOME/bin
    116 ./rview
    117 }}}
    118103
    119104== Third-party clients ==