[ previous ] [ next ] [ threads ]
 
 From:  "Jonathan De Graeve" <Jonathan dot De dot Graeve at imelda dot be>
 To:  "Manuel Kasper" <mk at neon1 dot net>
 Cc:  <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall-dev] RE: [m0n0wall] The future
 Date:  Wed, 12 Oct 2005 17:38:48 +0200
Haven't used it yet.

I took a PHP course to develop the things I had to add in m0n0wall since my work needed it.

Why don't follow a new course ;) (I always wanted to learn perl and I still have time :) )

> Much of the work on m0n0wall didn't go
>into just writing PHP code, but into figuring out how exactly
>configuration files for all the other daemons need to be written so
>that they do what we want them to do. These configuration templates
>can be copied almost verbatim from the existing PHP code, and
>translating the various conditional blocks and loops that put
>together more complicated configuration files would be no rocket
>science either. The same goes for the filter rules.

Yes and no, I indeed spent a lot of time in reading RFC's and figuring out the radius protocol, but
also the interaction between radius and m0n0wall and how it was integrated in m0n0wall.

I think if we chose a new programming language following criteria must be met:





BUT!!!
I think things should be kept as simple as is can.

>It's pretty clear that something needs to be done to the core code if
>we want to continue adding non-trivial features to m0n0wall in the
>future. I'd rather invest some time to learn from the past and lay a
>solid foundation for the future now than keep having to reinvent the
>wheel for each new feature later.

Indeed but I don't know what you didn't liked about the OOP functions of PHP. I didn't had problems
with it

J.

-- 
Jonathan De Graeve
Network/System Administrator
Imelda vzw
Informatica Dienst
015/50.52.98
jonathan dot de dot graeve at imelda dot be

---------
Always read the manual for the correct way to do things because the number of incorrect ways to do
things is almost infinite
---------

-----Oorspronkelijk bericht-----
Van: Manuel Kasper [mailto:mk at neon1 dot net] 
Verzonden: woensdag 12 oktober 2005 17:27
Aan: Jonathan De Graeve
CC: m0n0wall dash dev at lists dot m0n0 dot ch
Onderwerp: RE: [m0n0wall-dev] RE: [m0n0wall] The future

On 12.10.05 17:17 +0200, Jonathan De Graeve wrote:

> What about perl?
> 
> Supports, 00, is not TOO difficult and can be compiled directly to
> an executable :D

Why not? I haven't used perl much, and certainly never touched its OO
features, so I can't comment on its suitability - have you already
had some experience with it?

> But I still like to keep PHP since all the work people put into it.

That's another issue - of course, switching programming languages
would mean that most of the core code would have to be rewritten.
However, if you think about it, it's not that difficult with the
original PHP code available. Much of the work on m0n0wall didn't go
into just writing PHP code, but into figuring out how exactly
configuration files for all the other daemons need to be written so
that they do what we want them to do. These configuration templates
can be copied almost verbatim from the existing PHP code, and
translating the various conditional blocks and loops that put
together more complicated configuration files would be no rocket
science either. The same goes for the filter rules.

It's pretty clear that something needs to be done to the core code if
we want to continue adding non-trivial features to m0n0wall in the
future. I'd rather invest some time to learn from the past and lay a
solid foundation for the future now than keep having to reinvent the
wheel for each new feature later.

- Manuel

---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash dev dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash dev dash help at lists dot m0n0 dot ch