Jump to content
Xtreme .Net Talk

Recommended Posts

Posted

What is the difference between XML and XSLT?

What can I use XML or XSLT for (what's an example of its application)?

 

I'm asking these questions as I'm trying to decide which one to learn up...

Can you bind the beautiful Pleiades, and can you loose the cords of Orion? - God to Job...
Posted
so if i just pick up XML, will it be of any use then if i don't use XSLT?
Can you bind the beautiful Pleiades, and can you loose the cords of Orion? - God to Job...
Posted

XML is a method of formatting a file so you can get the information you want, it acts basically like a database.

<MyXMLDocument>
    <MyHeader Prop1="Hello">
          <Name>People</Name>
          <Address>23 Something Lane</Address>
    </MyHeader>
    <MyHeader Prop1="Hello Again" Prop2="Important">
           <Name>Someone</Name>
    </MyHeader>
</MyXMLDocument>

You use the readers in System.XML to parse these documents and get the info you want, Microsoft is pushing it as a replacement for INI files, it can also be used as a database.

.Net allows software to be written for any version of Windows and not break like Unmanaged applications unless using Unmanaged procedures like APIs. If your program uses large amounts of memory but releases it when something else needs it, then what's the problem?
Posted
i see, hm.......but using asp.net to connect to a database, would there still be any use for my program if i use XML? can these 2 be used together?
Can you bind the beautiful Pleiades, and can you loose the cords of Orion? - God to Job...
Posted

I'll try to answer one by one.

 

Q: would there still be any use for my program if i use XML?

A:

Well, it depends on why you would like to use XML in the first place.

If you would like to create web pages that seperate content from UI (-it's good to do so , for more detail search for MVC-), of course it would be good to use XML and then XSLT to convert them to HTML.

Q: can these 2 be used together?

 

A:

Well, it depends on the database you are using.

There are native XML databases and there are Relational Databases. Native XML databases (e.g. EXIST or Tamino) stored data as XML files. Relational database (e.g. SQL server, Oracle) stored data as tables.

 

Both of the database types still can accept XML, however if we use the former one (native xml database), it would be easier to store. It is still possible though to use xml together with relational databases. One can still actually traverse the XMLDocument object or XPathNavigator object and actually extract the data to store in the database, it would be quite slow though. Anyway, usually only a small part of the xml would be stored in database.

 

However, I've read that some relational database have ways too to store xml directly at a predefined format or even better, but I can't comment on those.

 

Hope the info is useful.

 

Best Regards,

 

David Lo

Posted

becoz from wat i understnad from the explanations above, XML can be more efficient than normal relational databases...

 

so in terms of developing an internet application, i'm not sure whether i should go ahead with ASP.NET or can i use 'em together? still undecided about it...is it advisable to use them together for the same webpage?

Can you bind the beautiful Pleiades, and can you loose the cords of Orion? - God to Job...
Posted
i see, okay, i am learning ASP.NET now, in the process, but was curious becoz many modern internet apps seem to involve hype about XML, so i also want to try it out, but wat can i use it for? in wat kind of applications then?
Can you bind the beautiful Pleiades, and can you loose the cords of Orion? - God to Job...
Posted
Think of XML as just a much improved and standardized way of structuring data, just like how AndreRyan illustrated in an earlier reply. It is not a programming language like ASP.NET so you can't build apps w/ it, but a markup language like HTML. You can use it in any application if there's a requirement to structure data in an "XML-like" manner. The links provided by Bucky should give you a good tutorial on what XML is all about.
Posted
When you learn ASP.NET you can use XML from within your ASP.NET applications, you will still use ASP.NET but instead of communicating with Relational databses, you can if you want use XML files instead.
Dream as if you'll live forever, live as if you'll die today
Posted

hm.........interesting, ah man, means i'll have to get an XML book...

 

okay, just another question, er.....are there any so called "guidelines" as to when i should use a relational database or when i should use XML files for storing data? which would be appropriate so i can decide...

Can you bind the beautiful Pleiades, and can you loose the cords of Orion? - God to Job...
  • *Experts*
Posted

One of XML's strong points is that it's universal; any XML parser

application on any platform can get the same data from a file.

XML web services exploit this ability in a good way: they

return data in a specific XML protocol, SOAP, so that anybody can

interpret it.

 

So if you're looking for interoperability, that is, transferring data

beteen apps, languages, and platforms, XML is the way to go.

"Being grown up isn't half as fun as growing up

These are the best days of our lives"

-The Ataris, In This Diary

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...