[THIN] Re: replacing RDP protocol stack with something else

  • From: "Webmail" <web@xxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Sun, 5 Oct 2003 23:17:25 -0400

Try this one too... (just click cancel if you get a security screen)
http://www.thinclient.net/technology/tsappdev.doc

JK

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Tom Morrison
Sent: Sunday, October 05, 2003 9:30 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] replacing RDP protocol stack with something else


I have a slightly different application, and I don't want
to use RDP as the transport mechanism.

It has been confirmed to me that it should be possible
to do this, but I am confused as to exactly what pieces
I would need to write/replace (and how to do this customization)

The pieces I am expecting I will need to deal with are:

        1) I will need to have some type of "kernel server" piece
                that detects client connects (via my own transport 
                mechanism).

                a) Question is: what API would I communicate with
                        to "instantiate" a terminal session

                        I am assuming it has something to do with the
                        Terminal Server, but where is the API/behavior 
                        defined for this?

        2) It looks like I need to write a custom Kernel layer 
                Device Display Driver - for each of these thin clients
                that would capture the display data for these "virtual" 
                clients - to be transported over by custom Ap...

                a) How do I register for just these session objects
                        (or is this something I will know when I know how to
                        write kernel layer Display driver...:-)

        3) KVM, I will have KVM Data to input from the remote client - 
                what API will I call/send this data to (with what API/behavior)

        4) Audio Out - assuming another kernel level driver to capture
                the data...

        5) Registering client devices (i.e.: audio, mouse, ...etc)

I am sure all the information I need is somewhere hidden in all the 
layers of documentation (RTFM, but I am also sure some of you also 
have that knowledge and point in the right direction quicker than my
stumbling...

I also assume that some of this will be answered by knowing how to write
a Device Driver (Display) in Kernel Level. I have the DDK, and am planning 
on learning how to build a basic kernel level drivers anywayz...(side bar, 
are there any good tools besides the Win DDK to write drivers)

Any/all info on this subject would be **greatly** appreciated!

Sincerely,

Tom Morrison
SoMnyRds@xxxxxxxxxxx
http://thethin.net/citrixlist.cfm
********************************************************
This Week's Sponsor - Emergent Online
Essential Thin Client Utilities.
Meet Jim Kenzig of thethin.net at the Emergent Online
Booth #24 at Citrix iForum on October 13th.
http://www.go-eol.com 
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
New! Online Thin Computing Magazine Site
http://www.OnDemandAccess.com

For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm

Other related posts: