Posted: Wed Feb 01, 2006 12:23 pm?? ?Post subject: InspIRCd 1.0 Final Released
InspIRCd 1.0-Final has been released. "The 1.0-Final release marks the point where we consider InspIRCd ready for production use on production networks, with enough features to be usable on any network from one user to ten thousand and above. For those of you who don't know what InspIRCd is yet, it is a scaleable, high performance expandable IRC server package, which offers many of the features of other IRC servers in a well designed modular form", the InspIRCd website announced.
This version includes a lot of new features, listed here, of which we picked a few prominent features and requested more information about them from developer Brain:
One of the new features is Message/Notice Flood Protection and Join Flood/Cycle Flood Protection which can be set with channel modes. We asked Brain if this has been tested on fairly large networks as well, as this seems quite intensive for the IRCd. "We tested this with a large number clones on my local network, and short of actually having tens of thousands of real people at my disposal, is usually a pretty good test", Brain starts. "It doesnt take up much in the way of cpu time to do what this module does, as it is done without using any types of timers and the checking is simple addition and subtraction; however it does add a slight overhead to each channel's memory usage, required to hold the various counters. This is where the benifit of modules comes into play -- if your network considers that these overheads are not acceptable, then it is simple to just not load the module and omit the feature :)"
Ban exceptions and Invite exceptions are standard now. With these two modes you can supply masks that are not affected by +b and +i channel modes.
One interesting feature is the +z channel mode, which allows only SSL clients to join, making a secure environment for those who wish so.
One of the projects that made InspIRCd known is their goal for getting meshlinking to work, by now, the holy grail of IRCd coding. The first attempt did not worked out too well. We asked Brain if developped has now stopped for it. "We temporarily placed mesh linking on hold until after the 1.0.0 release, after which point we have a few plans we wish to implement. These plans are still very much theoretical but most likely at least one of them will be implemented, which involves keeping redundant links active and switching links when a netsplit occurs using a 'reduced' netburst, saving bandwidth", Brain replied.
The IRCd's current recommended method of linking is the traditional treespan which is provided by the m_spanningtree module.
_________________
Asmo
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
???
