--Boundary-02=_ETirB/1XariFjSL
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Mittwoch, 1. Dezember 2004 20:21, schrieb Aaron Seigo:
> On December 1, 2004 8:53, Jakub Stachowski wrote:
> > - random idea I just got (not even started yet) for easy launching remo=
te
> > apps (not whole session): add new submenu to standard k-menu: 'K ->
> > Remote application -> (list of hosts) -> (normal k-menu for every host)
> > '. List of hosts could be populated by searching for _remoteapps._tcp
> > (advertising location of /usr/share/applications and ssh port) or
> > something similar.
>
> i don't think this would be very efficient, really. a better way might be
> to add support for mDNS to the FreeNX server and client. this would solve
> the big issue of how to do automatic discovery for NX on the network. it
> could also advertise applications that the NX admin has approved for use
> over the network, and that should be a bit more controllable/efficient.
>
> what do you think?

As FreeNX is not spreaded everywhere today and does not support single=20
applications (or is this in the stable release meanwhile?) such a simple=20
support for launching single remote application via traditionell X might be=
=20
very welcome by some. Promoting FreeNX next to it is of course a good idea,=
=20
too :)

=46riedrich

--Boundary-02=_ETirB/1XariFjSL
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBriTEECqmVFXwdrMRAl3hAKCRskTt3zagsII+pr3L3p4QV2hb2ACfRtqO
ixQCW/Vp/05hZtZh5J/95f0=
=OVZo
-----END PGP SIGNATURE-----

--Boundary-02=_ETirB/1XariFjSL--