A Hilton wrote:
>
> PMFJI, but nope. Although that's the common usage of a website, that's
> certainly not the only way it is done. A website (using an application
> called a web server) is, simply put, a server application that processes
> requests/posts on behalf of a client and returns results. The client
> application can be a web browser (either being controlled/not controlled by
> a human being) or any other type of application (ie Automated application to
> application) that can 'talk' over the required ports and use the correct
> syntax. All done with the menial web server. :)
That is the best explanation yet. It is indeed a B2B you describe - and
uses the web, but not the way it was intended. However, it would get
around the firewall problem.
Refining that a little, the "web" is just being used as yet another
internet transport facility. Do you see a reason why this cannot be used
for any B2B approach, even trad-edi?
Thank you for that contribution.
--
Ken Steel ICARIS Services
Email: [EMAIL PROTECTED]
Technology: http://www.icaris.net/
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
