XML, CGI, and VB6
in, our vendor would send an XML file to http://myserver/myprogram.exe
Next, how would I setup a test so that I can send myself an XML file
and test my processing of it?
More information if necessary. And I'm sure it will be because I'm out
of my league here...
The vendor that I am dealing with is going to send me data in 1 of 2
formats. Either CGI as a request string of the format
http://myserver/mycgi.exe?name1=value1&name2=value2...etc -- probably
in POST format, but that doesn't matter -- I already know how to write
a CGI program with VB6 and receive get or post data. The other option
is they will send an XML file. I just don't quite understand how I
would receive an XML file, but my company WANTS to receive XML instead
of cgi, so that it will be easier to integrate with other apps, and
because eventually the vendor may do away with CGI and go purely XML.
Anyone have any pointers for me? I've tried searching the net on this,
but my lack of understanding of what I'm doing is making my searches
way too generic.
Thanks for any and all pointers.
"YYZ" <firstname.lastname@example.org> wrote in messageYou mention CGI. Are you restricted from using Microsoft Web products?
>2 questions: How would I receive an XML file over the internet -- as
> in, our vendor would send an XML file to http://myserver/myprogram.exe
> Next, how would I setup a test so that I can send myself an XML file
> and test my processing of it?
> More information if necessary. And I'm sure it will be because I'm out
> of my league here...
Because if you have IIS (and therefore can write some ASP pages) you can
create a "pseudo-web service" to accept an XML stream (which is simply a
text stream) and then pass if off to a COM component that you could write in
Not at all restricted from using MS products. I've just never used ASP
before... But that sounds easy enough to do. All I need to do for the
XML thing at this stage is receive, make sure it contains certain bits
of information, then save it out -- we will do some heavier processing
later on, but the vendor requires that we respond back with 5 seconds
of receiving the file, just letting them know we got it and there
weren't any initial red-flags.
Thanks for the advice. The only reason I said CGI is that that is what
I'm comfortable with...I've written several hundred cgi programs that
take form input both GET and POST and respond with dynamic HTML to the
user...asp seemed like such a kludge compared to how I was doing it,
but I honestly never gave it the consideration it is probably due
If it ain't broke...