[Xastir] The future, how soon? B-)

[Jack Twilley]

WARNING: Unsanitized content follows.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Curt" == Curt Mills <archer at eskimo.com> writes:

Curt> I was actually thinking something more along the lines of SSH
Curt> for connecting, which should provide excellent security but is
Curt> probably overkill.

You'll have to be careful how you use SSH here, as the FCC still
frowns on encrypted traffic, and it's certainly not unreasonable to
assume that someone might tunnel the IP segment of xastir over AX.25.

Curt> Ok, you're assuming a single xastird daemon is the traffic cop
Curt> for the system.  We could do that, or we could split xastird
Curt> into two daemons, xastird which only talks to the storage
Curt> module, and xastir-clientd which services clients, talks to the
Curt> storage module and perhaps directly to xastird as well.  The
Curt> second configuration would allow us to have a very lightweight
Curt> configuration on the server, just xastird and the storage module
Curt> most of the time when clients aren't needed.

The single-daemon design is superior, in my opinion.  The win in
abstracting out the storage daemon is just too little to justify the
added complexity, but that's just me.

Curt> I tried some time back to ask for a switch to C++ or Java.  It
Curt> appeared to fall on deaf ears.  The original app was written in
Curt> C and I think most of the developers had experience in C, but
Curt> not the others.

Curt> This may be time to switch to something else.  Then again, may
Curt> not.

Let's see the design before a language is chosen.

Jack.
(shouldn't this be on xastir-dev instead?)
- -- 
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFA3GsYGPFSfAB/ezgRAitnAKD5LnUDfw55Nr2zQMGV4aptugsPUwCdFyOq
T8l5qWqpyliXVdPU0izbWIY=
=S8O1
-----END PGP SIGNATURE-----