Re: [Tigervnc-devel] File transfer

2009-04-14 Thread Peter Åstrand


I agree. Also, it wasn't just the implementation that was broken - the 
special protocol had many problems as well. I would say that the design 
was flawed from the start: If a file transfer feature should at all be 
included in a VNC implementation, it should at least be based on some 
existing protocol. Reinventing the wheel is always bad.


In ThinLinc, we are using NFSv3 and the unfs3 server. Works great.

Best regards, 
Peter Åstrand


On Mon, 13 Apr 2009, DRC wrote:


We may have discussed it before the list was created, because I can't
seem to find the thread in the archives.  However, IIRC, the reason was
mainly that the feature was broken and we didn't have anyone who cared
about it enough to fix it and maintain it.  File transfer only exists in
the Windows VNC server, and one of the reasons why we forked the project
was so we would be able to focus more on the Unix VNC server.  Don't get
me wrong-- we're still shipping WinVNC and VNCviewer.  In particular, my
project still has a vested interest in the Windows TigerVNC code.
However, the Windows code may not receive as much attention from the
project as a whole.

Matt Campbell wrote:

Hello all:

I noticed that file transfer was removed from TigerVNC about a month
ago.  Why was this done, and is there any plan to bring file transfer
back?  If the decision has already been explained, I'd appreciate a link
to the original explanation.

Thanks,
Matt

--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel


--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel




---
Peter Åstrand   ThinLinc Chief Developer
Cendio AB   http://www.cendio.com
Wallenbergs gata 4
583 30 LinköpingPhone: +46-13-21 46 00--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel


Re: [Tigervnc-devel] File transfer

2009-04-14 Thread Matt Campbell
Hello Peter:

Thank you for your comments.  The file transfer feature in the VNC4 
branch of TightVNC always felt flimsy to me.  The UI was especially 
inadequate for keyboard-only users.  I made several modifications to the 
UI, which I would contribute back to that branch of TightVNC if it were 
still actively developed.  I also agree that it would be better to use a 
standard protocol; I suppose SFTP would be a good choice.

Matt

--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel


Re: [Tigervnc-devel] File transfer

2009-04-14 Thread DRC
Well, except for that fact that it would require building TigerVNC
against OpenSSL, which has its own set of issues.  Why not just set up a
separate SFTP or SSh server on the Windows server?  I use the Cygwin SSh
daemon to accomplish this, but there are others that are easier to set
up.  There are also many free/open source SCP/SFTP/SSh client GUIs
available for Windows.


Matt Campbell wrote:
 Hello Peter:
 
 Thank you for your comments.  The file transfer feature in the VNC4 
 branch of TightVNC always felt flimsy to me.  The UI was especially 
 inadequate for keyboard-only users.  I made several modifications to the 
 UI, which I would contribute back to that branch of TightVNC if it were 
 still actively developed.  I also agree that it would be better to use a 
 standard protocol; I suppose SFTP would be a good choice.
 
 Matt


--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel


[Tigervnc-devel] File transfer

2009-04-13 Thread Matt Campbell
Hello all:

I noticed that file transfer was removed from TigerVNC about a month 
ago.  Why was this done, and is there any plan to bring file transfer 
back?  If the decision has already been explained, I'd appreciate a link 
to the original explanation.

Thanks,
Matt

--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel


Re: [Tigervnc-devel] File transfer

2009-04-13 Thread DRC
We may have discussed it before the list was created, because I can't
seem to find the thread in the archives.  However, IIRC, the reason was
mainly that the feature was broken and we didn't have anyone who cared
about it enough to fix it and maintain it.  File transfer only exists in
the Windows VNC server, and one of the reasons why we forked the project
was so we would be able to focus more on the Unix VNC server.  Don't get
me wrong-- we're still shipping WinVNC and VNCviewer.  In particular, my
project still has a vested interest in the Windows TigerVNC code.
However, the Windows code may not receive as much attention from the
project as a whole.

Matt Campbell wrote:
 Hello all:
 
 I noticed that file transfer was removed from TigerVNC about a month 
 ago.  Why was this done, and is there any plan to bring file transfer 
 back?  If the decision has already been explained, I'd appreciate a link 
 to the original explanation.
 
 Thanks,
 Matt
 
 --
 This SF.net email is sponsored by:
 High Quality Requirements in a Collaborative Environment.
 Download a free trial of Rational Requirements Composer Now!
 http://p.sf.net/sfu/www-ibm-com
 ___
 Tigervnc-devel mailing list
 Tigervnc-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel