Open nhoening opened 12 years ago
I suggest that insert
writes to two files. One is the complete shared history. As it would be inefficient to query that file for the shared-widget, it can also write to a file that only contains up to n
entries (so if there are already n
entries in there, insert
deletes the last and then inserts the new one).
Will sharing become very inefficient if the complete history file becomes very large? Yes, and then the file should be arhived (either by hand or automatically) and a new one should be started. But that does not have to be done in a first version of this.
A user hosts a simple XML file, to which driveby-sharing appends.
gritttt.php
needs no imports andinsert
only does some XML operation on the file. Also,gritttt.php
performs basic session management to implementcheck_login
(open: how to do some simple password-comparison - maybe store a password in a separate PHP file ...).