Is TightVNC enable HTTP access in Ubuntu 9.04?

[cmdmac]

Is TightVNC enable HTTP access inUbuntu 9.04?
I use sudo apt-get install tightvncserver in the terminate and I can use VncViewer to view the ubuntu, but i cann't use webbrowser to view the utuntu.How can I access ubuntu in other pc with webbrowser?
Thanks!wait for help!Sorry for my poor english.

[D-cat]

VNC is desktop sharing, not file sharing. If you want files shared, you need to install an HTTP or a FTP daemon. I use vsftpd, but if you prefer httpd for compatibility reasons (more apps can load files from http and ftp), that's perfectly fine. I found a video tutorial you might find helpful.

Install a Local Web Server on Ubuntu | Lullabot

[ptkobe]

Sorry, but why the f**k would "TightVNC enable HTTP access inUbuntu 9.04?"

Sorry for my f**cking english, just didn't get it.

Regards
Luis

PS:I just saw D-cat have post a reply. I'll just leave mine this way, if you don't mind

[cmdmac]

because TightVNC or other vnc version enable you use a webbrower or a vncviewer client to view the remote computer.
I have solved this problem just now~~

[ptkobe]

Good for you

[cmdmac]

Thank you for your answer.
I have solved this problem.It must install a tightvnc-java in linux.
run "man vncserver" can get this messge:
-httpport int
The http port to use for the java client applet (you have to
install the tightvnc-java package to make this work).

[ptkobe]

Well, never had heard of it. Googled about it. Thank you.

Regards
Luis

[D-cat]

The java client was known, and is usually not enabled by default because of the security risk invitation that's perceived from having the ability to control your desktop from a web browser. I didn't know if that was what you meant or not, but I had the figuring that the java client is slow, it doesn't give any functionality over a binary client, which exists for all common OS's.

The glaring weakness of VNC is the lack of ability to share files between the server and client as it's strictly a visual desktop representation, which is where httpd or ftpd fill in the gap. Using a protocol designed for file transfer to suppliment a VNC session means there's almost nothing utilitarian you can't do remotely.

Back on 04, I actually used VNC for remote video editing. If I had to do that today, I'd probably use NX for the sound server option, but point being, remote desktop is pretty amazing. Sorry I made the wrong guess. Enjoy your VNC.