On Tue, Jan 13, 2009 at 3:38 PM, Geoff Flight <[email protected]> wrote:
> Never having really written such an app Ive still wondered why you would use
> XML vs binary. Why would you use a verbose data description in a situation
> where bandwidth is relatively limited? That said, I now need to write a web
> service and that has convinced me to use binary and not XML. Everyone raves
> over XML and frankly, I don't get it. IN a closed architecture I see no
> point at all.
-------------------------------------

Because you were tossing around in your vernacular "cursors" of data.
They could be very complex instead of just a single sql return from a
data source.

I had one Customer Object that was well it had the kitchen sink in it.
 If I asked for any customer I would get back a plethora of data, more
than I ever needed to do a single task, but I didn't design it either.
 hahahahaha

In reality I got who the customer was, a list of all orders they did
within a year,  a list of all open invoices they had, a list of any
issues in the past that they challenged our quality, a list of
anything that was not yet shipped all packaged within the customer
object.  It rocked for filling out any page you ever needed to for any
requestor, it also clogged the crap out of our server when lots of
reps would be looking at their big clients before commission checks
were cut!   Oh did that cause time outs!

So you can see good idea goes to overkill and nobody would fess up and
agree that it was killing our network.

Some clients had lists in the thousands  of documents, hundreds of
invoices, and hundreds of docs in process.  The lists of their earlier
problems was in some cases huge as well.

So what I am saying is that you have to design instead of throw
together.  concepts like Less Is More are true, but nobody ever seems
to figure that out till you get into timeout issues.

To say that your going to go binary sounds great, it is just overhead
on both sides of the coin that you have to deal with.  Compress the
outgoing and decompress the incoming.

YMMV

-- 
Stephen Russell
Sr. Production Systems Programmer
First Horizon Bank
Memphis TN

901.246-0159


_______________________________________________
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.

Reply via email to