On Sep 14, 2006, at 12:46, Joshua Edelstein wrote:
> John: that suggestion would certainly have worked, but
it wound up
> being
> unnecessary. What wound up happening was that the
story was
> automatically
> assigned back to the only desk to which the user had
write
> permissions.
> Typically this would have been transparent, but because
the user's
> corrupt
> account caused so much load on the system just in
trying to access
> it, that
> took about 20 minutes to happen. In the past, we used
to have a
> challenge
> where stories would wind up being reassigned to the
first available
> desk, as
> appeared alphabetically. THAT was confusing, but
Kineticode came
> to the
> rescue.
Yes, but *why* the user's workspace is killing the system
is another
question!
> David: you may have noticed in my original message that
I'd already
> mentioned that all browsers experience the challenge.
 I
> anticipate you!
Uh, right.
D
|