[X2Go-Commits] page changed: wiki:development:roadmap

[wiki-admin at x2go.org]

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2015/02/05 08:56
Browser     : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0
IP-Address  : 188.105.114.57
Hostname    : dslb-188-105-114-057.188.105.pools.vodafone-ip.de
Old Revision: http://wiki.x2go.org/doku.php/wiki:development:roadmap?rev=1423126415
New Revision: http://wiki.x2go.org/doku.php/wiki:development:roadmap
Edit Summary: 
User        : stefanbaur

@@ -70,17 +70,19 @@
  **General improvement on documentation**
  
  Task assigned to: Stefan, aided by Mike#1 (hard to say, Mike#1 will coach Stefan for an equivalent of 4h to get things straight, no matter how long it takes)
  
- <del>**HTML5 Client**</del>tagged as unrealistic given current budget
+ <del>**HTML5 Client**</del> tagged as unrealistic given current budget
  
  If budget remains, a HTML5 client would be nice.
  //There seems to be a disagreement amongst the developers regarding how such a client should
be implemented.//
+   - One option would be to copy what other remote solutions are using - which means sub-par performance compared to our native NX/X2Go speeds.
+   - A from-scratch approach would bring native speeds, but is a time and money sinkhole.
  
  Task assigned to: <none yet> - could be Alex, Mihai, ...?
  
  
- <del>**Alternative to NX-Rewrite**</del>tagged as unrealistic given current budget
+ <del>**Alternative to NX-Rewrite**</del> tagged as unrealistic given current budget
  
  h1 has some ideas what other F/LOSS codebases might be suitable as a time- and money-saving alternative to doing the NX-Rewrite.
  He should mention them on x2go-dev to get more feedback, then a competent C/C++ coder should look at the alternatives and evaluate them for suitability.
  



-- 
This mail was generated by DokuWiki at
http://wiki.x2go.org/