Re: [service-orientated-architecture] Epperson on SOA & High Performance

[Steve Jones]

I'm not sure it does imply a weakness, given that SOAP is a text based protocol (size wise inefficent) and that compression of text is one of the best understood areas in IT then I'd say its one of those areas where two simple things work well together.  I've regularly used compression on websites, paticularly in the days before broadband was more widespread, and the beauty of the solution is that it has zero impact on the actual solution architecture, in effect its the same as adding more network bandwidth.

Steve

On 30/10/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:

Steve Jones wrote:
> When ever everyone talks about bloated on the wire, I always wonder if
> they've turned HTTP compression on, its not exactly tough to add gzip
> into Apache and that really reduces the bandwith as text compression is
> pretty effective.

One of my key measurements of a technology's capabilities and design soundness
is the number of third party technologies you need to add on to actually make it
usable/useful. I think its important for technologies to provide enough
'knowns' that a developer has no issues with knowing what things the technology
will 'see' around it which can impact performance and viability of the designed
application/system.

This particular 'fix' for XML kind of makes my skin crawl because it implies
that as a developer, I can't guarantee any particular performance because I
might need my customers to deploy into a particular environment that I can't
make a part of the solution such that they won't have to worry about it.

Gregg Wonderly

__._,_.___

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___