From freenx-knx Tue Aug 23 08:31:37 2011 From: chris () ccburton ! com Date: Tue, 23 Aug 2011 08:31:37 +0000 To: freenx-knx Subject: Re: [FreeNX-kNX] NoMachine NX 4 client and FreeNX Message-Id: X-MARC-Message: https://marc.info/?l=freenx-knx&m=131408832004858 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0168276524993103487==" This is a multipart message in MIME format. --===============0168276524993103487== Content-Type: multipart/alternative; boundary="=_alternative 002ED724802578F5_=" This is a multipart message in MIME format. --=_alternative 002ED724802578F5_= Content-Type: text/plain; charset="US-ASCII" freenx-knx-bounces@kde.org wrote on 22/08/2011 15:17:30: > I think FreeNX is broken and needs to be fixed to add NXPlayer support. It's hardly broken Marcelo, just slightly different. I'm not sure why you have expectations of forward compatibility. > If NXPlayer is working fine with nxserver, then nomachine will not fix > it to work with FreeNX. The nxclients aren't Open Source anyway and nomachine are not making their V4 libraries Open-Source so you may well find they make it all work by updating the V3 server to a subset of the V4 protocols and discontinuing all support for the V3 libraries, including the V3 client so we may be on our own now anyway. I guess Nomachine aren't too enamoured of FreeNX. > > The problem is that FreeNX is not 100% compliant with > NXServer and it is > hard to do that. I doubt it needs to be unless you want multimedia support. If you want NXplayer to work ASAP then :- install Nomachine's own Free Edition and disable packet encryption and sniff the packets contents and tell us what is happening during a session set up. > > Regards. > > On Mon, Aug 22, 2011 at 9:29 AM, Florian Schmidt wrote: > > hmm, tested with the latest Version of nx player (NX4 client). Sorry > > to say but it seems that this is still broken. It's unlikely that anyone will want to spend much time on this until Nomachine have finished beta testing. If you are in a hurry Florian, then you can sniff the session set up as described earlier. If you are lucky there might just be some trivial message re-formatting holding you up. Welcome to Open Source, you want it, you (help) fix it, or you wait. > > > > Cheers, > > Florian > >> > >> Nomachine also say . . . > >> > >> Compatibility between the 3 and the 4 will be fully preserved. > >> There may be bugs when connecting with a client 3 to a server 4 and > >> viceversa. > >> These bugs will be resolved in the final release. There's not much point in doing anything until you know Nomachine's NXPlayer actually works with Nomachine's server V3 AND the V3 nxagent/libraries . . . Does it, anyone ?? --=_alternative 002ED724802578F5_= Content-Type: text/html; charset="US-ASCII"
freenx-knx-bounces@kde.org wrote on 22/08/2011 15:17:30:

> I think FreeNX is broken and needs to be fixed to add
NXPlayer support.
It's hardly broken Marcelo, just slightly different.

I'm not sure why you have expectations of forward compatibility.

> If NXPlayer is working fine with nxserver, then nomachine will not fix
> it to work with FreeNX.


The nxclients aren't Open Source anyway
and
nomachine are not making their V4 libraries Open-Source
so
you may well find they make it all work by updating the
V3 server to a subset of the V4 protocols
and
discontinuing all support for the V3 libraries,
including the V3 client
so
we may be on our own now anyway.

I guess Nomachine aren't too enamoured of FreeNX.

>
> The problem is that FreeNX is not 100% compliant with
> NXServer and it is
> hard to do that.
I doubt it needs to be unless you want multimedia support.

If you want NXplayer to work ASAP then :-

install Nomachine's own Free Edition
and
disable packet encryption
and
sniff the packets contents and tell us what is happening during a
session set up.

>
> Regards.
>
> On Mon, Aug 22, 2011 at 9:29 AM, Florian Schmidt <fschmidt@gmx.at> wrote:
> > hmm, tested with the latest Version of nx player (NX4 client). Sorry
> > to say but it seems that this is still broken.
It's unlikely that anyone will want to spend much time on this
until Nomachine have finished beta testing.

If you are in a hurry Florian, then you can sniff the session set up
as described earlier.

If you are lucky there might just be some trivial message
re-formatting holding you up.

Welcome to Open Source, you want it, you (help) fix it, or you wait.

> >
> > Cheers,
> > Florian
> >>
> >> Nomachine also say . . .
> >>
> >> Compatibility between the 3 and the 4 will be fully preserved.
> >> There may be bugs when connecting with a client 3 to a server 4 and
> >> viceversa.
> >> These bugs will be resolved in the final release.
There's not much point in doing anything until you know
Nomachine's NXPlayer actually works with Nomachine's server V3
AND
the V3 nxagent/libraries . . .

Does it, anyone ??


--=_alternative 002ED724802578F5_=-- --===============0168276524993103487== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ________________________________________________________________ Were you helped on this list with your FreeNX problem? Then please write up the solution in the FreeNX Wiki/FAQ: http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ Don't forget to check the NX Knowledge Base: http://www.nomachine.com/kb/ ________________________________________________________________ FreeNX-kNX mailing list --- FreeNX-kNX@kde.org https://mail.kde.org/mailman/listinfo/freenx-knx ________________________________________________________________ --===============0168276524993103487==--