Hi Roland, > >>>> They say that they also intentionally change it to break > clients that aren't qualified.
> this one is buried behind a firewall, so it requires a > client that can negotiate the firewall. They whipped up such > a client > in .NET. There may be a java client, though I've not seen it > yet. Either these guys don't understand their own system, and are just faking their way through it by spewing buzzwords and jargon - or they are purposely misleading you. Intentionally breaking their API as a security measure is nonsense. I'd fire the person that came up with that idea. And if a .NET client can negotiate their firewall, then so can a Java app and Witango. Either they have a firewall port open, or not. A port is a port is a port. 80 operates no different than 3333 or 64444, and <@URL> can call HTTP on a custom port, last time I checked. > well, the way it SEEMS to work is that the notion of web services > enables machine-to-machine information interchange. Platform > independent, etc. > > To > my way of thinking, it defeats all that standards platform > independent formatting stuff as you have to have their client to hit > their service. Why bother with SOAP? Seems like a waste of effort. Yeah, seriously I don't think these guys know what they're talking about. SOAP over HTTP is not rocket science and is a fine solution, unfortunately the IT staff at Choicepoint is the wrong people to manage it. I know this doesn't get you any closer to a solution, but at least know this isn't hopeless. So maybe you can ask to speak to someone who knows what they're talking about at this place? I wish I had the time to help you out, but I don't unfortunately (I have a fulltime contract right now that is not a small job) - I'd love the opportunity to throw their BS back at them. Best of luck. Scott Cadillac, Email: [EMAIL PROTECTED] http://scott.cadillac.bz ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
