/haiku/src/servers/app/ |
H A D | ServerTokenSpace.h | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
/haiku/src/apps/remotedesktop/ |
H A D | RemoteView.h | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
H A D | RemoteDesktop.cpp | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
H A D | RemoteView.cpp | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
/haiku/src/servers/app/drawing/interface/remote/ |
H A D | StreamingRingBuffer.cpp | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
H A D | StreamingRingBuffer.h | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
H A D | NetSender.cpp | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
H A D | NetReceiver.h | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
H A D | NetReceiver.cpp | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
H A D | RemoteDrawingEngine.h | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
H A D | RemoteHWInterface.h | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
H A D | RemoteDrawingEngine.cpp | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|
H A D | RemoteHWInterface.cpp | 5ed41cffff30e38974623d0586c36524209cb08e Tue Nov 21 19:44:56 UTC 2017 Michael Lotz <mmlr@mlotz.ch> RemoteDesktop: Switch connection direction and simplify client.
Instead of the server connecting back to a listening client, make it into a more traditional setup with the server listening on a port and the client connecting to it.
The client can now either connect directly, unencrypted and without the ability to trigger listening and specifying a command, or through SSH, as before with the possibilty to run a target application and causing the creation of the listener.
With the direction change, there's only the need for one, local, port forward with SSH, which simplifies things.
|