[Seaside-dev] Initial Request Failure on Retry
Philippe Marschall
philippe.marschall at gmail.com
Sat Mar 16 09:05:20 UTC 2013
On Thu, Mar 14, 2013 at 7:12 PM, Ken Treis <ken at miriamtech.com> wrote:
> We have build something using the Seaside-Rest add-on, and everything works beautifully in GemStone until a transaction conflict triggers a retry -- at which point we get a 404 rather than the expected response.
Can you provide a bit more detail about the retry code? Where (server
adapter,filter, ...) does it run and what does it look like?
Thinking about it you may actually need a bit more than just resetting
the path consumer. The properties on the request context and the
response buffer as well.
Cheers
Philippe
More information about the seaside-dev
mailing list