Re: [phpBddb-dev1] dbase design

[Brian <br...@br...>]

TO: php...@li...
SUBSCRIBE TO THE LIST IF YOU HAVEN`T DONE YET !

Hi,

first i want to stress out, that i want the single server solution to be 
coded first. After having a release of that, we will decentralize the 
system, by creating one superhost, and allowing webmasters to implement our 
solution at their websites.

Now some words to your ideas:
3) is my favourite, with some addition/ changes we can discuss later on

The way how to reach communication between servers,  could only be to do 
html parsing.
This is because most webhosters do not allow to access database from a host 
different than `localhost` so we do not have the change to use SQL only.
We need PHP to interact between the servers. Well it`s not a new protokoll 
but we`ll have to create a command set, that allows servers to execute 
database command on each other.
For security reasons, this is also the best way because no server could/ 
need to have write access to the other,  they exchange data by parsing 
maschine readable html sites. We could use XML, or plain textfiles.

I do not agree that parsing needs much resources. The webserver does what 
he is used to do, offer webpages nothing more. If traffic is getting to 
high, we`ll could add a reload stop. Parsing itself is no intensiv calculation.

However our first aim is to code the webfrontend, that we can do some 
experiments on the subject. I need a working release, that i could 
distribute this project on some websites - that it becomes more popular and 
we can see, where changes are needed.

  I will subdivide the project into smaller pieces (usermanagment, viewing/ 
browsing function, editing function, etc.) so that we could start coding.
See my next mail for more details (which will include some more planning 
papers)

Brian

At 14:09 16.07.2002 +0300, Janis Putrams wrote:
>Hi!
>I am not sure if i have correctly understood but I think that I am getting 
>there.:)
>There would be many individual servers, which deal with their own 
>information, but we want one "big" that has information about all of them 
>and keeps them up to date. We can't use just one database because each 
>individual server has it's privacy. Is that right?
>Here are my thoughts about what could be possible solutions.
>We can't make pear-to-pear connections so there is basically three solutions:
>1) The central server is open to everybody and individual servers update 
>themselves and central database.
>2) Individual servers register with the central server and grant some 
>(read&write) access to it. So central server from time to time checks all 
>registered servers and using its privileges updates all individual servers.
>3) This one is basically combination of first two. The individual servers 
>register with the central server and get read privileges to update their 
>databases. Central server from time to time checks registered users and 
>updates central database with collected information from user individual 
>servers.
>
>The differences are in development and control.
>The first one is easy to make but has basically no control of individual 
>servers. They may update their own databases but not the central.
>Second one gives all control to the central database. Not all individual 
>server administrators would agree with that.
>Third one is compromise between first two. Individual servers must 
>register to update their own information. If central server can't update 
>information from a registered user the read access to that user is blocked.
>
>I don't know the exact situation so I really can't decide which could be 
>the best. Also I don't like the idea of developing some special protocol 
>or data format for data transfer. Parsing individual server HTML could 
>take a lot of resources and many errors could occur. I think it would be 
>best if we could use the same old SQL. :)
>Any comments would be great. Looks like there will be a lot of fun. :) Not 
>an easy one.
>
>Janis Putrams
>p.s
>Sorry for my English. Still learning..
>
>--> http://www.one.lv - your number one mobile email service!
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by: Jabber - The world's fastest growing
>real-time communications platform! Don't just IM. Build it in!
>http://www.jabber.com/osdn/xim
>_______________________________________________
>Phpbddb-dev1 mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phpbddb-dev1