RE: [cobalt-users] Re: Cobalt Wish List

["James Nesbitt \(IHQ Network\)" <ihq-network-lists@xxxxxxx>]

I like this wish list thing and you guys have a few good ideas here, just
wish I could contribute to the programming somehow; just my programming
skills in Perl is non-existant.

But here is a side thought, how easy would it be to apply the changes made
for the Raq550 to the Qube3?

Regards,

James Nesbitt

-----Original Message-----
From: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Bruce Timberlake
Sent: Thursday, January 08, 2004 09:08
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: [cobalt-users] Re: Cobalt Wish List


> 	- Modular architecture for application choices:
> 		For example, I would love to be able to choose my own DNS
> 		server instead of being forced to use "Bind". Why not
> 		extend the platform to allow users to choose their own
> 		MTA, Mailing List Manager, and Nameserver?

Abstraction of services for 1 common UI is a huge PITA and adds an extra
layer of complexity and slowness to the system, as hooks for djbdns,
bind, etc have to be built and fit into the existing system.  Rather
than dealing with each service "natively" you would need a generic way
to gather all the info that each service variation might need, and only
pass on whatever the actual installed system needed.

IMO, if you were to offer alternate services, the PKG/.deb/whatever
would have to include all the UI and "glue" code specific to that
service's application(s).  Meaning that the service maintainer has to
mess with the UI.

Worth investigating, for sure, though.

_____________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To subscribe/unsubscribe, or to SEARCH THE ARCHIVES, go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users