Hello Amin,
Have you had a chance to work on this?
Emmanuel
On 9 janv. 2010, at 15:59, Amin Mohammed-Coleman wrote:
> Hi Sanne
>
> Thanks for the advice! I'll take a look at it.
>
>
> Cheers
> Amin
>
> On Sat, Jan 9, 2010 at 1:34 PM, Sanne Grinovero
> wrote:
>
>> Hi Amin,
>> I've been looki
I forgot about this behavior, I thought you were raising an exception during
the sync mode (even if run with parallel processes). That definitely looks like
the right thing to do.
So an exception strategy should:
- know if it's a synchronized call or not
- know the list of operations that are
Hi Amin,
I'm looking at way too much stuff, it's very welcome that you look at
it. I didn't assign it to me as I've too much other stuff already
assigned.
Sometimes I do some experiments locally but I do only commit if it's
looking good, most of the time I need to bring something up here for
feedba
Hi Sanne
Thanks for the advice! I'll take a look at it.
Cheers
Amin
On Sat, Jan 9, 2010 at 1:34 PM, Sanne Grinovero
wrote:
> Hi Amin,
> I've been looking a bit in this, but didn't take any action as we
> didn't discuss any strategy, so glad you join in propose something.
> I didn't think of jm
Hi Amin,
I've been looking a bit in this, but didn't take any action as we
didn't discuss any strategy, so glad you join in propose something.
I didn't think of jms, it's ok we provide some way for the end user to
override whatever we provide, but I think we should just provide
the basic stuff: log
Hi All
Emmanuel asked me to look at this issue (HSearch 421) where exceptions
happening in backend process which are going unnoticed. I was wondering if
I could get some advice/thoughts on how to tackle the problem.The issue
mentioned providing the user the option to decide how to handle exce
