|
|
| Author |
Message |
ButtaKnife
none
Joined: 26 Apr 2005
Posts: 37
|
 Posted: Aug 27, 2008 9:36am Post subject: |
 |
|
| bctrainers wrote: | | darkwarrior wrote: | | I'm actually looking for services that also read from the SQL database, not just dumping stuff to them.. Would be nice to have web signups and web channel registrations too.. |
The only thing I really [personally] have always wanted on IRC services is mySQL databases for reading / writing / storing stuff to.  |
The trick is to find a good balance so that the services aren't dragged down by live SQL. Dumping to an SQL DB is easy with a seperate thread, but if services has to query for channel settings every time something happens... 
| katsklaw wrote: | | The only services I know of that read and write to sql are not modular, so if you wanted to add all those fancy features you requested, you'd have to find a coder willing to add them. One beautiful thing about modules is you don't need a dedicated coding team on your netwrk. |
I like modular programs, but your statement doesn't make a whole lot of sense. Modular or not, if you want something that isn't in your copy of services, someone needs to code it. |
|
| Back to top |
|
 |
katsklaw
Guru
Joined: 28 Jun 2004
Posts: 1114
|
| Posted: Aug 27, 2008 4:08pm Post subject: |
|
|
ButtaKnife, the difference is that with modules you can have dozens of authors, each contributing a little bit, or 1 feature at a time whereas without modularity, you are pretty much restricted to the core coding team. So people not even associated with your network can contribute and never even know it. Non-modular software would require shell access to the server.
For example, Anope has 3 active coders, 3 active QA members. there are literally hundreds of modules for various tasks written by dozens of people outside the Anope team. That wouldn't be possible if Anope wasn't modular.
Case in point, Epona. You can't just write code for Epona and share it with the world without modifying Epona's core, which will likely void any type of support Epona has. With modules you also can simply compile the module and load it without having to shutdown services and without having to re-compile the entire source. Likewise, in most cases you can unload the module too.
Modularity when written correctly can be extremely useful on many levels.
So in short, if it's not modular, it's likely someone that doesn't even care about your network has to accept your feature request or you "hire" a coding team .. modular systems don't. Yes someone still has to write it .. but in the case of Anope, there is a good chance someone has already written the feature you want. |
|
| Back to top |
|
|
mage
Newbie
Joined: 04 Oct 2006
Posts: 75
|
| Posted: Aug 31, 2008 6:52pm Post subject: |
|
|
Yes we have registered the project on sourceforge so as soon as we have the documentation ready we'll release it. Cannot say much just now but we'll keep the interested ones updated.
Thank you all for the suggestions!! keep throwing ideas Your nicks will be on the credits hehe. |
|
| Back to top |
|
|
|
|
| |
Register
Log in
