I am writing a comet application that has to keep track of each open connection on the server. I want to write an entry in the database for each connection, and every time I get the application new data (often), then I have to search the database for the proper connection, which is why I do not want to start wrongly Choosing the slow database software allows a footer to support a database that supports small, small pieces of data (rather sometimes large sized data)?
I suggest using a server platform which allows the creation of servers continuously, In such a way that all the information contained in memory will be limited to write access to all the databases (if you really want to permanently save any information), usually in specific comet-applications (such as chat / games) At least is less.
Databases are not created to keep such data directly from a database, it is always meant to create query strings, often they are also called DB servers (sometimes also on the network), DB lookup, results The ordering is sent back, sending deserialization and crossing the results obtained. No The way it can be as fast as possible to retrieve the value of memory.
If you really want to be with PHP, then I suggest you and the same caching server.
Congratulations - back2dos
Comments
Post a Comment