Home
last modified time | relevance | path

Searched hist:"5 ed41cffff30e38974623d0586c36524209cb08e" (Results 1 – 13 of 13) sorted by relevance

/haiku/src/servers/app/
H A DServerTokenSpace.h5ed41cffff30e38974623d0586c36524209cb08e 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 DRemoteView.h5ed41cffff30e38974623d0586c36524209cb08e 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 DRemoteDesktop.cpp5ed41cffff30e38974623d0586c36524209cb08e 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 DRemoteView.cpp5ed41cffff30e38974623d0586c36524209cb08e 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 DStreamingRingBuffer.cpp5ed41cffff30e38974623d0586c36524209cb08e 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 DStreamingRingBuffer.h5ed41cffff30e38974623d0586c36524209cb08e 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 DNetSender.cpp5ed41cffff30e38974623d0586c36524209cb08e 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 DNetReceiver.h5ed41cffff30e38974623d0586c36524209cb08e 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 DNetReceiver.cpp5ed41cffff30e38974623d0586c36524209cb08e 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 DRemoteDrawingEngine.h5ed41cffff30e38974623d0586c36524209cb08e 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 DRemoteHWInterface.h5ed41cffff30e38974623d0586c36524209cb08e 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 DRemoteDrawingEngine.cpp5ed41cffff30e38974623d0586c36524209cb08e 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 DRemoteHWInterface.cpp5ed41cffff30e38974623d0586c36524209cb08e 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.