Fri 21 Aug 2009 01:03:15 PM UTC, original submission:
Hello,
we know that CERTI uses the TCP protocol,
we know that some computers are using an HTTP proxy,
an interesting contribution has been to use this proxy to do
wide area distributed simulations,
but this can lead to an error.
That is to say, I download CERTI, I run the standard configuration
script (myCERTI_env.sh which includes CERTI_HOST=localhost),
I launch the billard federate and it does not work.
billard -n1 -fTest -FTest.fed
CERTI Billard 3.3.3cvs
with TIMESTAMP. If you want without TIMESTAMP add -e option.
RTIA:: RTIA has thrown NetworkError exception.
RTIA:: Reason: gethostbyname gave NULL answer for hostname <proxy>
with error <Resource temporarily unavailable>
or
billard -n1 -fTest -FTest.fed
CERTI Billard 3.3.3cvs
with TIMESTAMP. If you want without TIMESTAMP add -e option.
RTIA:: RTIA has thrown NetworkError exception.
RTIA:: Reason: Proxy connection refused: HTTP/1.0 403 Forbidden
I think that we should avoid that because this is the procedure
that we recommend to all the beginners.
Today the solution exists :
export CERTI_HTTP_PROXY=""
What happens ?
In this simplest case, CERTI tries to use the HTTP proxy
but it does not work or it does not agree the request.
Why to use this proxy in the case of a standalone computer
or in the case of a local network ?
TCP does not imply HTTP !
Even why to use this proxy if we can ask for the opening
of the good TCP port ?
Now the poll.
Do you prefer the introduction of a new variable when the
usage of HTTP is wanted ?
Do you prefer that we modify the standard configuration files ?
Do you prefer an intermediary solution: To discover that
the federation is working locally and to disactivate the
HTTP proxy usage ?
Thank you,
Pierre
|