[phpBddb-dev1] db design

[Janis P. <jan...@on...>]

Hi!
That is true that it is hard to tell how the project will develop and what will be requested. But also I think that planning is very important because there are things that would become unavailable if we didn't took them in account while writing the client front-end. For example if we agree to do HTML parsing in the future we should design HTML so that it would be easily parsed.
I agree that most firewalls and etc. require special configuration to access server on any SQL port. If that could be possible solution it would save us a lot of time. :(
What I meant w parsing was that if we are using HTML as the data format we also need an HTML parser. It means a lot of string parsing but I agree that XML could be a possible solution. I just took a look at php manual and I think it has enough XML parsing already built in.
If it is this way it could become pear-to-pear network. (Just an idea) Main server could have a list of running clients and that's all. Clients would update their pear list from server and get XML from each other. This would cause more traffic than client-server solution but as it was mentioned before web servers are made for that.

Now back to the real world... :)
I took a look at CVS and I noticed *.inc files. I suggest that we could better use something like *_inc.php because *.inc files require special treatment. If no configuration is done to web server they are shown in plaintext. I have seen folks get hacked because of this.;)

I am kind of new to CVS. I have worked w different systems but CVS is something I want to learn. Does anyone knows a good place to start with?

Janis


--> http://www.one.lv - your number one mobile email service!