[CLUG] IP Tables Front End Project
AJ McKee
aj.mckee at druid-dns.com
Mon Feb 21 15:02:42 GMT 2005
Hi Adam and All,
Thanks for the database stuf I was thinking of making a more simple
database structure but get where your coming from. Somthing like this
A Default services table with a listing of well known services
A Access table that contatins rules that allow access of all things
(Something Like this;
AccessID, From, TO, Port
A Deny Table
DenyID, From, To, Port
OtherRules
No idea here about what other rules are :)
I know your voteing for peardb and as I said I have no problems writing it
in peardb, but below are some of the reasons why I would still err towards
ADODB.
1. Its faster
2. User does not have to install pear db or keep it up to dat
3. Makes end deliverable nice and self contained
4. ADODB is written with commercial use in mind and therefore in fairness
to it (while this is not normally the case with oss projects like pear)
there is more consistancy in the support and its codebase.
5. C extension available for php making execution faster
6. Exception handeling is built into ADODB (Whihc means ease of porting to
php5 when the time comes)
7. it supports the pear syntax
Now I know this is nit picking and I am reluctant to go down this route,
but at the moment I feel ADODB is just as easy if not earier to work with
than pear, its more mature and stable and requires less messing around by
the end user, which is what we want to achieve. But I can see the drawback
when pear becomes much more popular as well, so its just my personall
choice at the moment. but I have said my bit and will go with what the
project group decides.
I am in agreement on it should be coded in php4 witht he cavet that as
much of it as possible is coded with php5 in mind.
Lets arrange a meeting anyhow sometime this week between all whom are
interested, get a pen and paper and sort out what needs doing etc. All in
favour say aye before wend and well sort out a venue.
Cheers
AJ
More information about the Cork
mailing list