Search the Community
Showing results for tags 'architecture'.
Found 2 results
-
I'm thinking about developing a website that will use the following dynamic architecture: index.php?id=1index.php?id=2index.php?id=3index.php?id=4etc. As opposed to the static (old school): index.phppage1.phppage2.phppage3.phppage4.phpetc. What are the pros and cons in terms of caching, search engine indexing and other stuff you can think of?
-
I'm working on a website that I want to be accessible to speakers of many languages but I'm wondering how to architect such a website. I seem to have two options and I hope you guys can help me choose: 1) Database I could make a table that lists all the messages and then have individual language tables with translations of those messages. Each page would then make a dozen or more queries to get all the messages/content to populate each page. I'm a bit worried about what the effect this may have on my databases and whether it is too much for them to handle in addition to all the other queries such as registration, login etc. 2) PHP array Using PHP arrays is also a popular solution. I think both MediaWiki (which drives Wikipedia etc) and phpMyAdmin go with this solution. It's easier to crowd source the translation this way since most people are familiar with pure text files. I'm worried about all the memory that is consumed by this approach and at what point it becomes inviable since every translation gets loaded into memory for every page request.
