The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
I want to write a messageboard system, and I'm in the thinking-about-it-sometimes-planning-stage. I'm currently considering a system which creates a file for each message created, and using a naming system where each first message has a number, then for each reply, you have the beginning post number, followed by a dot, then the number which is allocated to that reply. This would allow infinite (sort of, I hope, possibly only restricted by filename sizes) threads and sub-threads. However, this would mean all messages ever would be created as a file and stored.
So the question is, would this be a feasible idea? Would I have to regularly delete or archive the old messages. Is there a point in keeping old messages for prosperity, or something? I must admit, I hate it when I do a search and it comes up with a result from some random messageboard and you click the link and the page is missing, so would it be a good idea to keep them all?
The only other way I could think of would be to have a flat file database and have a line per message, as this is my normal method with perl/cgi/files ;) but this would require a ton of processing to sort into threads etc.
I must admit I was thinking along the lines of having directories for each thread, with the aformentioned naming convention, but while writing this post I realised I wasn't sure how the messages would exist within the system(!).
So, anyone got any ideas on messageboard writing? Anyone done it before? Possible the peeps who made this messageboard system could suggest some ideas - how do you store the messages? You have the easier task of having all the replies on one page, when I would rather have the sort of system you experience through Outlook Express with newsgroups, where replies are to a specific post.
Cheers,
Rikki
So the question is, would this be a feasible idea? Would I have to regularly delete or archive the old messages. Is there a point in keeping old messages for prosperity, or something? I must admit, I hate it when I do a search and it comes up with a result from some random messageboard and you click the link and the page is missing, so would it be a good idea to keep them all?
The only other way I could think of would be to have a flat file database and have a line per message, as this is my normal method with perl/cgi/files ;) but this would require a ton of processing to sort into threads etc.
I must admit I was thinking along the lines of having directories for each thread, with the aformentioned naming convention, but while writing this post I realised I wasn't sure how the messages would exist within the system(!).
So, anyone got any ideas on messageboard writing? Anyone done it before? Possible the peeps who made this messageboard system could suggest some ideas - how do you store the messages? You have the easier task of having all the replies on one page, when I would rather have the sort of system you experience through Outlook Express with newsgroups, where replies are to a specific post.
Cheers,
Rikki
Did you want to write a msg board because you want the coding practise or because you need one?
I have some code that I downloaded from somewhere, meaning to have a look at it myself. Its done using CGI (off the top of my head), and should work on Freeola, if you want me to pass it on.
I have some code that I downloaded from somewhere, meaning to have a look at it myself. Its done using CGI (off the top of my head), and should work on Freeola, if you want me to pass it on.
Also use MySQL as it is a lot faster than sorting through a huge filesystem. Apparently freemysqlhosts.com (or something like that) will work with Freeola.
Doesn't Perl/C++ have MySQL support anyway?
Doesn't Perl/C++ have MySQL support anyway?
I am afraid that Freeola don't support MySQL. If you use files then you do not need to archive. Just keep giveing then incrimenting numbers. Also use PHP as it is a lot lot faster then CGI especially when your site gets large.
Cheers, I was planning on using Freeola, so I would not be able to use MySQL. And I haven't had a chance to learn PHP yet, as the thought of having functional code and HTML in one file scares me. It's bad enough when I've done silly things like use JavaScript... Plus I like CGI, so nur :P
Anyways, if I go for the file per message system, has anyone got any ideas/opinions on the amount of archiving or deletion of old messages I should do?
Cheers,
Rikki
Anyways, if I go for the file per message system, has anyone got any ideas/opinions on the amount of archiving or deletion of old messages I should do?
Cheers,
Rikki
... well, if your planning to use it on Freeola, don't use MySQL.... I think the one File per Subject idea sounds best
For God's sake man, build it in PHP with MySQL!!!
I want to write a messageboard system, and I'm in the thinking-about-it-sometimes-planning-stage. I'm currently considering a system which creates a file for each message created, and using a naming system where each first message has a number, then for each reply, you have the beginning post number, followed by a dot, then the number which is allocated to that reply. This would allow infinite (sort of, I hope, possibly only restricted by filename sizes) threads and sub-threads. However, this would mean all messages ever would be created as a file and stored.
So the question is, would this be a feasible idea? Would I have to regularly delete or archive the old messages. Is there a point in keeping old messages for prosperity, or something? I must admit, I hate it when I do a search and it comes up with a result from some random messageboard and you click the link and the page is missing, so would it be a good idea to keep them all?
The only other way I could think of would be to have a flat file database and have a line per message, as this is my normal method with perl/cgi/files ;) but this would require a ton of processing to sort into threads etc.
I must admit I was thinking along the lines of having directories for each thread, with the aformentioned naming convention, but while writing this post I realised I wasn't sure how the messages would exist within the system(!).
So, anyone got any ideas on messageboard writing? Anyone done it before? Possible the peeps who made this messageboard system could suggest some ideas - how do you store the messages? You have the easier task of having all the replies on one page, when I would rather have the sort of system you experience through Outlook Express with newsgroups, where replies are to a specific post.
Cheers,
Rikki
So the question is, would this be a feasible idea? Would I have to regularly delete or archive the old messages. Is there a point in keeping old messages for prosperity, or something? I must admit, I hate it when I do a search and it comes up with a result from some random messageboard and you click the link and the page is missing, so would it be a good idea to keep them all?
The only other way I could think of would be to have a flat file database and have a line per message, as this is my normal method with perl/cgi/files ;) but this would require a ton of processing to sort into threads etc.
I must admit I was thinking along the lines of having directories for each thread, with the aformentioned naming convention, but while writing this post I realised I wasn't sure how the messages would exist within the system(!).
So, anyone got any ideas on messageboard writing? Anyone done it before? Possible the peeps who made this messageboard system could suggest some ideas - how do you store the messages? You have the easier task of having all the replies on one page, when I would rather have the sort of system you experience through Outlook Express with newsgroups, where replies are to a specific post.
Cheers,
Rikki