[Glass] How to produce an HTTP 204 response

[Richard Sargent via Glass]

I want to experiment with modifying Seaside under GemStone so that if/when
GRGemStonePlatform>>#seasideProcessRequest:adaptor:resultBlock: runs out of
retries, it produces (or causes to be produced from a high level) an HTTP
204 (No Content) response, rather than an Internal Server Error "Too many
retries" page.

Can anyone offer advice on how to do this?


In this scenario, each iteration throws a WASessionLockNotAcquiredException
because another web server gem is holding the session lock for a long
running request. This only occurs when running multiple web server gems
behind a HA Proxy (or any other load balancing mechanism, I expect) and an
impatient user clicks the link/button again.


Bonus points for anyone who can definitively tell me whether the 204
response from the second gem would or would not prevent the user's browser
from showing the results from the first request/first gem when it finally
completes. With the current implementation, the Internal Server Error "Too
many retries" seems to prevent the display of the results from the original
request when it finally completes.


Thanks everyone!




--
Sent from: http://forum.world.st/GLASS-f1460844.html