From: Brian <br...@br...> - 2002-07-15 08:19:37
|
Hope you had a nice weekend! Well i agree, that client to client application are hard to create with PHP only. This is not what i want. I prefer the single server solution, but everyone can set up the 'phpBddb' server due this is open source. There are serveral interested websites, dealing with the subject beer mats. Let's say just two of them and i set up a server. Then i want be sure, that they update each other. This could be done by PHP. Therefore every server needs websites, which are maschine readable, like CSV tables. This pages could be fetched by another server manually, or automatically by cronjob. But as you said, our first goal must be the single point solution. Did you configured your CVS client that you can do changes to the code? I tried to tidy up a bit. Do you thing it is better to start new code, or doing changes to my test code? PS: Please subscribe to our mailinglist. Brian At 23:26 14.07.2002 -0500, you wrote: >I was looking over the diagram. I don't understand why there needs to be >more than one at this point at least. one decent server can handle a >very large number of users at once. I suppose that later on we can >create a more distributed cluster of server that all the clients can >connect to to store information on. > >I'm not sure that the idea to use only PHP/Mysql to set up the client to >client applications. PHP is not designed for that, for one it is a >serverside scripting language. it defeats the purpose of client to >client if you have to run the script through a server. > >using Mysql and PHP to build a interactive web service is cool...but I >would think that it would be difficult to run a serverside script on a >client to client basis unless each user was running there own server. >that is unless I'm mistaken... > >David |