Re: [Aaron-devel] What language to use for aaron (short and long term)?

[Sean C. <sea...@it...>]

	A few other comments I've gotten and need to respond to:

> What language is this in?

	Prototype:  Ruby
	Long term:  C or C++

> Is this going to be only for the web?

	Nope.  This is an abstract project in the sense of Apache 2.0. =20
It's a framework that theoretically could replace Cron.  If you take the=20
terminology of what I've written and change query with action, and=20
action with reaction, you've got a system that promises to be much more=20
sophisticated than cron and substantially more flexible.

> Is it going to be in C?

	Yeah, I think so.  C is the universal language of UNIX and even=20
windows.

> I still think it is a bad idea to prototype anything in Ruby, because
> the language is so young.

	It's more mature than PHP and has been around since 1995.  With=20
the following module support, I think it's a little hasty to think that=20
it's that young.

http://sean.chittenden.org/programming/ruby/ruby_modules.rbx
http://sean.chittenden.org/programming/ruby/programming_ruby/lib_standard.h=
tml
http://sean.chittenden.org/programming/ruby/programming_ruby/builtins.html

	It seems sophisticated enough to me.  I'm on the ruby-talk and
ruby-cvs lists and there aren't many bugs in the language that I've seen
come up.

> What type of databases are we going to keep information in?

	State information is stored in memory in the aaron daemon. =20
Aaron is a persistent application that isn't called by crontab and is
instead started/stopped at bootup by an rc.d script.  Because I'm a big=20
believer in abstraction, I think it'd be entirely possible to have state=20
information stored in a database if the module was loaded that'd store=20
stuff there instead of via direct ruby variable calls.

> Are we talking about crontabs?

	A possible replacement for crontabs.

> Or there own daemon running?

	Own daemon.

> All of these needs to be done, before we can start on anything?

	There 'ya go.  Check out the ROADMAP and start chipping away at=20
the config files for various protocols and resources.

	-sc

--=20
Sean Chittenden