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

[Hurt, Gerald]

>> *) xastird. 
>> *) Storage module.  This can be flat files, db files, SQL Database.
>> *) Map import module.

>> *) Map and Message client. 

For the sake of migration how about adding an interface to the current
xastir? Include a place for password to xastird and check boxes for the
services the daemon will provide (communications, map service, messaging,
etc.) Once you open the socket, you're authenticated until the thread
closes. Of course each "service" could have a separate interface also.

Now we would have the ability to use existing clients with the "new xastir"
which could be developed modularly.

I think Aaron's /etc/xastir.conf idea is a great way to handle permissions.

Jay
73 de N0XVB

---
Jay Hurt
Emergency Call Relay Center (ECRC)

Intrado Inc.
1601 Dry Creek Drive
Longmont, CO 80503
email: gerald.hurt at intrado.com

Intrado
www.intrado.com 

ATTENTION:

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify Intrado Inc. immediately at 720.494.5800 and destroy all copies of this message and any attachments.