On 6 Dec 2010, at 15:27, Mark Ritchie wrote:
...
Patches welcome!
...
On 7 Dec 2010, at 11:30, Patrick Middleton wrote:
[3] adequate uniqueness could instead be created by ensuring that
when httpd forks, the child process resets uniqueID_str.
Here's a patch. The changes work for me wit
Patrick Middleton schrieb:
And so to the subject line of this message: "x-webobjects-request-id
lacking uniqueness?" Of those 24 chars, the first 16 are effectively
fixed whenever httpd starts,
> and I appear to be seeing values being
reused for the last 8.
It sounds
an instance (this header is not
> > "leaked back" to the client) and this appears to be unique: 24 chars long
> > corresponding to three hexstrings of 32-bit numbers, being the time at
> > which some initialization code was called in the process (httpd), the
> &
On 6 Dec 2010, at 15:27, Mark Ritchie wrote:
Good Morning,
On 6/Dec/2010, at 5:09 AM, Patrick Middleton wrote:
If an instance receives a request via a direct action and I don't
want it to be redirected via the load balancer, enough information
is broadcast such that other instances waiting
Good Morning,
On 6/Dec/2010, at 5:09 AM, Patrick Middleton wrote:
> If an instance receives a request via a direct action and I don't want it to
> be redirected via the load balancer, enough information is broadcast such
> that other instances waiting for requests will be able to tell that anoth
On 6 Dec 2010, at 14:20, Simon wrote:
i was thinking the same - alternatively:
- do whatever is you are doing in a background thread
- switch on concurrent request handling, as i presume that it is
actually the request that is blocking, not the DB as unless your
are using something like m$
que: 24 chars long
> corresponding to three hexstrings of 32-bit numbers, being the time at which
> some initialization code was called in the process (httpd), the process
> identifier (of httpd), and a unique sequence counter defended by a lock.
> The point at which this header
On 6 Dec 2010, at 13:52, r...@synapticstorm.com wrote:
Hi Patrick,
Couldn't you just use WOLongResponse so that it keeps the first
connection alive until it responds?
Regards,
Rob.
Without going into too much detail -- no.
---
Regards Patrick
OneStep Solutions (Research) LLP
www.oneste
t which this header is added means that a redirected request will have
> the same x-webobjects-request-id header.
>
> And so to the subject line of this message: "x-webobjects-request-id lacking
> uniqueness?" Of those 24 chars, the first 16 are effectively fixed wheneve
dded means that a redirected request will have the same x-
webobjects-request-id header.
And so to the subject line of this message: "x-webobjects-request-id
lacking uniqueness?" Of those 24 chars, the first 16 are effectively
fixed whenever httpd starts, and I appear to be seein
10 matches
Mail list logo
