× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



> From: Brad Stone
> 
> The HTTP protocol isn't THAT conveluted, maybe you're
> referring more to the form of the POST data in the request
> (the SOAP/XML stuff).
> 
> Feel free to contact me and I can work with you to get
> something working.

Oh no, HTTP is fine, Brad, it's the stupid SOAP stuff.  I like
Narayanan's HTTP request, that looks easy enough (except I'm sending
large amounts of data in the parameter).  The problem is that as far as
I can tell, Narayanan's request doesn't work with WebSphere, at least
how I've got it set up.

Right now, I just want to make sure I understand the protocol.  Once
that's done, then I figure out how to automate it.  I'm sure I'll be
trying to take advantage of your expertise at that point <grin>.

By the way, there's a REALLY nice Windows TCP/IP sniffer out there that
Mark Waterbury pointed me to - Colasoft's Packet Analyzer.  It's not
cheap ($200) but it's pretty impressive.  My only problem is that it
doesn't seem to trace local requests; I don't know if that's a Windows
thing or a Packet Analyzer thing.

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.