Making ngIRCd work with services
Hi everyone, Scott Perry and I are going to be working to make ngIRCd work with services. To begin with, we'll try to make it work with atheme and IRC Services, hopefully this will make us (more?) compatible with other services packages as well. As an aside, Scott and I are enjoying learning German from the comments in the code. Eric Grunow
egrunow@ucsd.edu <egrunow@ucsd.edu> wrote:
Scott Perry and I are going to be working to make ngIRCd work with services. To begin with, we'll try to make it work with atheme and IRC Services, hopefully this will make us (more?) compatible with other services packages as well.
Wow, thats great news!
As an aside, Scott and I are enjoying learning German from the comments in the code.
Heh, patches to get rid of those are appreciated. Also, i'd be happy to help out if you have any problems. Thanks, Florian
Hi Eric! Am 20.04.2008 um 07:21 schrieb egrunow@ucsd.edu:
Scott Perry and I are going to be working to make ngIRCd work with services.
That is really good news, services are the most requested feature ngIRCd is lacking actually.
To begin with, we'll try to make it work with atheme and IRC Services, hopefully this will make us (more?) compatible with other services packages as well.
Just for the records: http://www.atheme.net/ There are usually two approaches when implementing services: (1) emulate an IRC server, (2) use a serices interface ("special commands"). I think the latter is much cleaner.
As an aside, Scott and I are enjoying learning German from the comments in the code.
Hehe ;-) ngIRCd startet as a very little "research project" of myself just to prove that it is possible to write an IRC daemon that is not utter crap. In the beginning I never thought that the project would develop that good that it would be usable as a regular IRC daemon, that it would be used by others, and that "someone" would care about it more than 7 years later. Because I was coding "just for me" in the beginning, I didn't think a lot about the coding style and language used. Looking back that has been a mistake ... So, if you have problems to understand the comments and/or the code, please feel free to ask! And for the future, we - should use english comments, - write clean code following our "modern" coding style, - have a look at contrib/ngindent :-) Best regards Alex
On Apr 20, 2008, at 13:16, Alexander Barton wrote:
Just for the records: http://www.atheme.net/
There are usually two approaches when implementing services: (1) emulate an IRC server, (2) use a serices interface ("special commands").
I think the latter is much cleaner.
I agree that it's cleaner, but I also think it's less generic. Since the goal is to get "services" working with ngIRCd as opposed to a specific services package, I don't think we're really allowed to pick what we support. One of the reasons we're looking at atheme in particular is because I interact with the developers on a daily basis. The less we have to worry about problems with the services themselves, the more we can concentrate on ngIRCd itself.
And for the future, we - should use english comments, - write clean code following our "modern" coding style, - have a look at contrib/ngindent :-)
That sounds good. As we go through the code we'll make try to make changes towards these ends. ./scott
Hi Scott! Am 21.04.2008 um 04:14 schrieb Scott Perry:
On Apr 20, 2008, at 13:16, Alexander Barton wrote:
Just for the records: http://www.atheme.net/
There are usually two approaches when implementing services: (1) emulate an IRC server, (2) use a serices interface ("special commands").
I think the latter is much cleaner.
I agree that it's cleaner, but I also think it's less generic. Since the goal is to get "services" working with ngIRCd as opposed to a specific services package, I don't think we're really allowed to pick what we support.
One of the reasons we're looking at atheme in particular is because I interact with the developers on a daily basis. The less we have to worry about problems with the services themselves, the more we can concentrate on ngIRCd itself.
I do not recommend to invent a "new" services interface, but to use one of the interfaces used by other servers. I'd highly like to see services registered and counted as "service" by ngIRCd (and not as "server"). But I think the author of the atheme services package can give you much better advice than me, so most probably you should simply ignore me and ask him what he would recommend :-) Regards Alex
participants (4)
-
Alexander Barton -
egrunow＠ucsd.edu -
Florian Westphal -
Scott Perry