Xml

I'm beginning to see the advantages of using XML for data storage as opposed to the old faithul (MySQL). I've got one problem though. With MySQL you get inbuilt security - in order to modify or read the database you need a username and password. How is XML any more secure than just sticking a .txt file in your webspace? I've been hacked before and its I just don't see how you can stop people from going through your site at will and finding and editing the files.

I don't know all that much about storing data with XML but I assume when accessing an XML file you will need to provide some sort of a key that will grant access to the data.

I think i've decided not to bother...XML is nice, but looking at all the tutorials and stuff i've found on it, managing it is absolute hell...

Well, so far the only advantage I see in using XML is that you can use XML without needing ASP or PHP available on your server. If you have access to those I really don't see any reason for using XML.

If anyone can post some good examples of when and why you would use XML I'd appreciate it...I need to teach it in a few months and I'm having difficulty finding something to be excited about with XML...

You could put the XML data into a table in MySQL

There are huge differences. It all depends on what you're gonna use the data for. For static data that doesn't have to be manipulated, XML is a markup that can be passed from e.g. php to perl to .net and still contain and show the same stuff.
So it's great for web services, and passing though tiers.

You can rather easily install a httpmodule or modify the server-settings, not to let .xml files be gotten withour requiring authorisation.

Using a databases allows for relations. It allows for stored procedures. It allows for SQL. Data is easily gotten. Databases are mostly used for data storage. XML is more of an intermediate language - to use if you don't know what type of tier comes next. Hence asynchronos javascripting and xml and not asynchronos javascripting and tables; because then the data is language specific.

recommended read:
http://msdn.microsoft.com/library/de...tml/boagag.asp

Depending on what you are using for, one is better than the other. Obviously, for sharing data remotely, you can be placing the data in an xml file, but alternatively, you can be using a webservices as well, which would be the prefered method.

You can save xml files as server-side files such as .asp or .php or whatever language you usually use, and then include it, or find a way so that only your server internally can call it and nobody else.

But if you are using it for yourself, there really is no advantage to xml files. I would say stick with MySQL client.