ok now...it's not a bad article...it's just one of those where you have to think to yourself...why? Why do it this way...it makes a simple task...complex.
It sounds from the article that using xml is making all this amazing stuff possible. When in fact, adding items to a cart, deleting items from a cart, making sure old or discarded carts do not take up database space and speeding things up is in fact a benefit derived from using a session based datastore in the application and has nothing to do with xml really. Xml doesn't really make this a more flexible application...but does introduce more fail points and greater component complexity.
The benefits, on the client side are minimal if at all and in fact if done properly with or without xml it should look clean, When your code is properly applied and encapsulated.
The benefit I see from using xml in the web application space is the decoupling ability it gives you. Which is not really exploited in the article above, being it is shown as a tightly coupled application.
Using xml correctly should allow my application to decouple, exploit inherent interfaces and use services in a .net world. I see no reason to use xml and tightly couple in external components that I didn't need before, unless it's just as an exercise to try out xml. Any well written array produces a better effort in your session.
Like I said...not really a bad article, but why?
Discussion on:
View:
Show:
This was developed for a classic ASP shop that comprised of mostly former COBOL/VSAM/CICS developers who relied on Design Time Controls way too much. First and foremost it was part of an effort to demonstrate that a recordset could be transformed to XML, which could then be bound to HTML. Later, the shopping cart became part of an effort to demonstrate that ASP.Net would make life better because XML would be easier.
As a consultant, I merely offer suggestions and examples of better ways. The client gets the final say in the choice of technologies. This was simply an educational tool using technology that was already paid for.
As a consultant, I merely offer suggestions and examples of better ways. The client gets the final say in the choice of technologies. This was simply an educational tool using technology that was already paid for.
Web building is a complex undertaking. Many stakeholders are involved. Here's a quick glance at some forces acting on the situation.
Internet shoppers want to browse, select and purchase the what is right for them. They want the site to be useful and easy-to-use. No waiting for page refreshes. No silly update cart button. Just "this is what I want so give it to me." The seek and ends and have seen the means. Best deal. Why should I pay? I'm not a good shopper if I don't get the best deal.
Developer wants to make it quickly. Easily. No Fuss. No angry clients. Just great code. Stuff that works. Reliable. No unexpected side-effects. Wham. Bam. Others want to learn, develop and explore. Try this and that. See what works better. See if they can work better. Prove themselves. Do the world good.
In the midst of all this turmoil is the technology. The pure mechanics of code, silicon, with its own constraints and limitations. The technology must be arranged well. What well means depends on how closely the arrangement "fits" the demands of the stakeholders.
The store owner wants some peace, serenity and tranquility. She wants sales! Her kids are growing up, they need an education, Bessy wants to be a doctor. The store owner wants the best for her family, herself and her friends. It is her dad's birthday soon. He's almost 60. He's in a home. Lonely guy. Damn! That developer e-mailed again talking about some X EM EL whatsit. Stuff it. Too hard. Too confusing. It's night now.
Database, Wires, Code, More Code, Code, Wires, Interface, Screen, User, Eye, Nerve, Brain, Nerve, Hand.
The data must flow through all these parts. Connected. Unbroken. Truthful, whole and confidential.
So many factors and variables. In all this, what really matters? Just do it.
Internet shoppers want to browse, select and purchase the what is right for them. They want the site to be useful and easy-to-use. No waiting for page refreshes. No silly update cart button. Just "this is what I want so give it to me." The seek and ends and have seen the means. Best deal. Why should I pay? I'm not a good shopper if I don't get the best deal.
Developer wants to make it quickly. Easily. No Fuss. No angry clients. Just great code. Stuff that works. Reliable. No unexpected side-effects. Wham. Bam. Others want to learn, develop and explore. Try this and that. See what works better. See if they can work better. Prove themselves. Do the world good.
In the midst of all this turmoil is the technology. The pure mechanics of code, silicon, with its own constraints and limitations. The technology must be arranged well. What well means depends on how closely the arrangement "fits" the demands of the stakeholders.
The store owner wants some peace, serenity and tranquility. She wants sales! Her kids are growing up, they need an education, Bessy wants to be a doctor. The store owner wants the best for her family, herself and her friends. It is her dad's birthday soon. He's almost 60. He's in a home. Lonely guy. Damn! That developer e-mailed again talking about some X EM EL whatsit. Stuff it. Too hard. Too confusing. It's night now.
Database, Wires, Code, More Code, Code, Wires, Interface, Screen, User, Eye, Nerve, Brain, Nerve, Hand.
The data must flow through all these parts. Connected. Unbroken. Truthful, whole and confidential.
So many factors and variables. In all this, what really matters? Just do it.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
