php + mysql of xml?

[FlashFocus125]

Wat gebruik ik best voor het maken van een fotoalbum?
is de beste keuze php + mysql of gebruik ik beter xml.
kan ik rond xml een cms maken? hoe werkt dat dan met sql enz?

Gr

[Dauntless]

Misschien is dit (http://flashfocus.nl/forum/showthread.php?t=1882&highlight=php+mysql) wel interessant voor je ? :)

[Stuf]

op gotoAndLearn (http://www.gotoandlearn.com) staat nu een goeie tutorial hierover..

mss heb je er wat aan..

[mech7]

Ik zag laatst ook dit op de macromedia site...

http://www.macromedia.com/devnet/dreamweaver/articles/xml_overview.html


f XML Stores Data, is XML a Database?

Since XML stores and describes data, it resembles a database. You've probably already heard the words "schema," or "query language" mentioned in relation to XML. What makes then XML different from a typical DBMS (database management system)?

First of all, XML is portable. While databases rely on the specific database language they were designed for in order to be correctly interpreted, XML carries its meaning in its tags. XML is self-describing, which means it carries both the structure and the semantics of the data, while databases can only define the structure of data.

Furthermore, XML can represent data as hierarchical trees, as you have seen in the previous section. For instance, the <employee> element is a child of the <department> element, and is embedded as such in the XML tree.

Of course XML also has its drawbacks when compared to databases, but this is normal, since they were designed with different goals in mind. The most obvious disadvantage is that XML lacks database-specific features such as triggers, multi-user access, efficient storage, indexes, security, transactions, data integrity checks, or queries across multiple documents. This is normal, considering that a DBMS is designed for manipulating, storing, and retrieving data in a fast and secure way, while XML was designed to exchange data across platforms.

Consequently, searching in XML documents is also slower, because of the lack of indexes and search optimization features, common to databases.

Also, XML is more verbose, requiring a pair of tags and/or attributes for each data item.

While the data-centric/document-centric divide is somewhat obsolete, it is nevertheless important for understanding the XML philosophy and the main concepts behind the XML technology.




* XML should not be used on small, personal websites, or company presentation websites, which are scarce in content or have just a few pages. Static HTML and some CSS/Flash design can better do the trick.
* XML should not be used on websites with a vast amount of content, where data retrieval and security are paramount. In this case, databases provide a much better solution. Such applications may include corporation websites, data warehouses, etc.
* XML should not be used to replace HTML or to replace databases. If your website is already database-driven, there is no point in switching to XML. You can, however, add a RSS feed to carry news or company announcements and let your clients import them directly in their websites.

[mech7]

Je kan trouwens wel met xml een cms maken, op www,sitepoint.com staat hele tutorial hierover..

Wat gebruik ik best voor het maken van een fotoalbum?
is de beste keuze php + mysql of gebruik ik beter xml.
kan ik rond xml een cms maken? hoe werkt dat dan met sql enz?

Gr