That's a good answer. I just get a little sick of the XML-evangelists who tout using it for everything. AS always, once you strip the hype away you find that a particular technology has its advantages and disadvantages, times to use it and times not to.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Russell Sent: Wednesday, 14 January 2009 9:18 AM To: ProFox Email List Subject: Re: [NF] M$ is pushing ahead for performance On Tue, Jan 13, 2009 at 5:23 PM, Ricardo Aráoz <[email protected]> wrote: > It's probably me but I didn't get your answer to Geoff's question. > Come again? Why in a closed architecture would you go for verbose data > description when bandwidth is limited? > Please consider that foolish solutions like sending more info than > needed may be implemented in both solutions with equal ease. ------------------------- I live in a web world for the past 5+ years and xml is a natural solution to consider. It's another markup plain and simple. In the end to me I will be shooting you html, and containers of data for dropdowns as well as list objects. These in XML is the smartest and fastest way to have worked per java developers, or VS developers working in a web environment. You can query xml, find what your looking for and change it if need be. That is fantastic. If you say you only work in a windows app and not a web app I say that your in a closed space that is not growing, only shrinking. What if my data access could feed both web and win environments? I would be writing it one time and exposing it for either flavor of client. In all honesty you don't want to push a ton of data, your bandwidth isn't as large as anyone thinks it is. Having a dropdown list of 1000 items is foolish. Having a grid for data presentation that holds 200 rows is close to being as bad if the data row is wide. People have loved the pagination idea in web to cover their butts when you show 8 rows of the grid and you have 300+ for them to see. I can't open the demo from the site I presented this morning, I don't have 2008 here. :( This week is nuts in getting many things ready for the ski trip or Cursillo in 3 weeks. I probably wont get to look at it till Feb., but I want to see how they are working with binary! Is it easy to put in or is it a whole new layer that doesn't abstract well with others? But the Q asked was why use it? My answer is ease of use first and foremost with respect to web data. It is listable and it is queryable. If you write it once can it be used by other types of clients? Sure! How are you going to differ from this? User clicks on Button "Add Client" what are you going to do today in your binary implementation? -- Stephen Russell Sr. Production Systems Programmer First Horizon Bank Memphis TN 901.246-0159 [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
