General information
Title:
Application logic and XML
(Also posted in .NET Forum)
I'm under the impression that every piece of application logic that I write is a fancy combination of 3 things:
1. Getting data
2. Transforming data
3. Putting data
For example, get some data from a database (1), calculate a total from the data (2), and display it to the user (3), and store the total back in the database (also 3)
If this is all application logic is, using two standards, XML (which includes XSLT) and IP, hypothetically we should be able to get data from anywhere, transform it into anything, and put it somewhere else (or back from where we got it).
Are there examples of business logic that cannot be written as transformations? IOW, Are there examples of applications that cannot be described completely in XML?
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only