[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Firewall question
Scott Klement wrote:
. . .
> Unless you mean that the request has actually ARRIVED on the server, and
> the server folks can see the request? In that case, ignore everything
> I've said :)
Yes. We definitely know the request arrived. In fact, two requests
arrived within the space of less than a second, which can only happen if
the first call to http_url_get_raw (with the domain URL) immediately
returned something other than 1 (in this case, -1), but its request
still reached the server. (Or if the first one was delayed in arriving
for exactly as long as it took http_url_get_raw to return an error, and
the second one, with the dotted-decimal IP address, arrived instantly).
========================
In pseudocode:
Client:
Call http_url_get_raw to access our web service by domain name.
If that call fails, immediately try again by dotted-decimal IP.
If that call fails, display an error message including the return code.
====
Server:
Receive a request.
If the request is a POST, in the format of our older web service,
process it (not relevant here).
If the request is a GET, in the format of our new web service:
{
Log the request.
Call the RPG program that processes the request.
RPG program generates response data, and logs it, with timestamp.
Frame the response data from the RPG program as an HTTP response.
Send the HTTP-formatted response.
}
If the request is not valid for either web service, send a generic
negative response.
=========================
The two requests (both properly formatted for the web service) generated
calls to the RPG response generator within the same second on the RPG
TOD clock.
--
James H. H. Lampert
Touchtone Corporation
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------