Results, Not Resolutions

Results, not Resolutions 2002-01-24
Anonymous

Results, not Resolutions 2002-01-24
Gary McGraw

Results, Not Resolutions 2002-01-24
David Litchfield (2 replies)

Results, Not Resolutions 2002-01-24
davep (at) pitt (dot) edu [email concealed] (1 replies)

Results, Not Resolutions 2002-01-25
Nicholas Harring

Results, Not Resolutions 2002-01-25
Anonymous

Results, Not Resolutions 2002-01-24
Anonymous (1 replies)

Results, Not Resolutions 2002-01-24
Anonymous

Results, Not Resolutions 2002-01-25
Anonymous

No SOAP? How do you do remote procedure calls over the web? 2002-01-25
Anonymous (6 replies)

No SOAP? How do you do remote procedure calls over the web? 2002-01-25
Anonymous

Well, I think the point was no SOAP-over-HTTP, not to have no SOAP at all. The deliberate overloading of a program-to-program communication protocol within web protocols will force network security engineers to proxy all web traffic so it can be examined by the firewall at the application layer. That sucks on several levels.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/articles/315/10143#10143

No SOAP? How do you do remote procedure calls over the web? 2002-01-25
Anonymous

Your Homework! 2002-01-25
Anonymous

No SOAP? How do you do remote procedure calls over the web? 2002-01-26
Anonymous

Well, to conclude: Use Java, M$ 2002-01-25
Anonymous (1 replies)

Well, to conclude: Use Java, M$ 2002-01-25
Trithemius (1 replies)

Well, to conclude: Use Java, M$ 2002-01-25
Anonymous

Results, Not Resolutions 2002-01-25
Anonymous

Results, Not Resolutions 2002-01-25
BMaximus

SOAP Recommendation is Silly 2002-01-25
Anonymous (1 replies)

SOAP Rec is correct 2002-01-26
Anonymous

Almost right on the compensation 2002-01-25
Anonymous

Results, Not Resolutions 2002-01-25
Anonymous