In fact there where an error in the called URL we forget to add at the
end of the URL the RPC servlet url-pattern.
So In post we where just asking the index...
Now this have been corrected, we have an answer which is 405 or 500
depending on how we construct the CURL or WGET request.
So we still
We've noticed on our application that sometime some RPC does not
answer.
When we load the index.html every this is correctly started, but when
user try to login = send an RPC to check is user/pass he never
receive an answer.
Actually we didn't have a clue why we do not have answer and the only
On 03/22/2011 10:06 AM, Mogoye wrote:
We've noticed on our application that sometime some RPC does not
answer.
When we load the index.html every this is correctly started, but when
user try to login = send an RPC to check is user/pass he never
receive an answer.
Actually we didn't have a
Well a RPC request will be done via HTTP/TCP so the only way to lost the
answer is when the server does not respond within TCP's timeout. If the
timeout is reached I think GWT will call the RPC request's onFailure method.
So as long as your servlet responds somehow, RCP requests should be fine.
