[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Binding an app to a protocol (KVNC)
From:       Jens Kristian =?iso-8859-1?q?S=F8gaard?= <jk () jksoegaard ! dk>
Date:       2000-04-28 15:24:26
[Download RAW message or body]

Dawit A <adawit@earthlink.net> writes:

> > > vnc://my.host:display/
> > > And get KVNC triggered, like the way a mailto url works. Does

> BTW, please use "vnc:/", instead of "vnc://" since this is not even a
> representation of some protocol in the true sense of the word.  Hmmm... on

Yeah, it is a protocol.

> the second thought maybe it is.  Anyways the main reason is not that but
> rather the fact that VNC is not a a heirarchial based protocol or resource
> representation at all.

Is it not?

Compared to HTTP, the parameters for a VNC connection using the VNC
protocol are:

        1. Hostname (just like HTTP)
        2. Screennumber (like the portnumber of HTTP)
        3. Password (just like HTTP)

The same applies for well-known standard URL's like:

        telnet://this.server.com

etc.


-- 
Jens Kristian Søgaard,
jk@soegaard.net -- http://www.jksoegaard.dk/
Søger du noget? -- http://www.google.com/
echo|perl -ple'$_+=4E-6*!int rand()**2+rand()**2while$i++-1E6'

[prev in list] [next in list] [prev in thread] [next in thread]