I'm looking to start a bunch of new projects. I've been using PHP/MySQL but I'm starting to wonder if that is starting to become obsolete. Especially considering the popularity of XMLHttpRequest and XML these days.
If you are making a site with tons of requests, would you be better off using XML or MySQL to decrease server load? What are the upsides/downsides of each?
Thanks in advance, you learned Jedis.
PHP/MySQL? Javascript/XML?
Moderator: General Moderators
Reply XML or MySql
hi aarongoos
i prefer you xml bcz xml is muchpower full then Mysql when you reciving thousands of hits
after 1000000 its comes to much slow its mine personal experince
xml will be benefical in speed security acesses
i prefer you xml bcz xml is muchpower full then Mysql when you reciving thousands of hits
after 1000000 its comes to much slow its mine personal experince
xml will be benefical in speed security acesses
- CoderGoblin
- DevNet Resident
- Posts: 1425
- Joined: Tue Mar 16, 2004 10:03 am
- Location: Aachen, Germany
My opinion...
Each has it's advantages but it is dependent on what you are trying to do. Even XML has to retrieve the data from someplace, even if it is the filesystem. You also need to create it, either yourself or someone else. You then need some method of validating it which depending on your users, may be problematic.
If you are dealing with relationship data then a relational database has it's place as that is what it is designed to do. If dealing with other data you may want to look at XML or JSON. Bear in mind, the use of XMLHttpRequest has it's place but it is not the be all and end all. There still remains the problem of user perceptions and informing the user that something is happening. If you need to perform initial startup every time you need to get some little bit of information, the overall load time will increase and you will need more total server processing time.
Each has it's advantages but it is dependent on what you are trying to do. Even XML has to retrieve the data from someplace, even if it is the filesystem. You also need to create it, either yourself or someone else. You then need some method of validating it which depending on your users, may be problematic.
If you are dealing with relationship data then a relational database has it's place as that is what it is designed to do. If dealing with other data you may want to look at XML or JSON. Bear in mind, the use of XMLHttpRequest has it's place but it is not the be all and end all. There still remains the problem of user perceptions and informing the user that something is happening. If you need to perform initial startup every time you need to get some little bit of information, the overall load time will increase and you will need more total server processing time.
-
d3ad1ysp0rk
- Forum Donator
- Posts: 1661
- Joined: Mon Oct 20, 2003 8:31 pm
- Location: Maine, USA
Somebodies been reading those buzzword articles again..
You want to combine the technologies to create the best situation.
XML isn't a replacemnt for mySQL, it's something that can be used hand in hand.
XMLHttpRequest isn't even close to PHP, it's used to make a request TO another page from javascript. It doesn't enable any server side functionality, you still need php/asp/cgi to do so.
You want to combine the technologies to create the best situation.
XML isn't a replacemnt for mySQL, it's something that can be used hand in hand.
XMLHttpRequest isn't even close to PHP, it's used to make a request TO another page from javascript. It doesn't enable any server side functionality, you still need php/asp/cgi to do so.