Re: outrigger "I/O error reading from mux connection"

Nirmalya Sengupta wrote:
> This thread of discussion was an excellent study on how
> clearly people in this forum think and how to make intelligent
> guesses about technical problems. After reading Lachlan's post,
> I tried to simulate and was successful. What I realized was that
> from the beginning, I had been using Transactions for any operation
> on the Space almost as a rule and therefore, I never came across
> this. This is a good test case to demonstrate the fall-out of
> a decision to not make a 'transaction' around a 'write' operation.
>

I may have misunderstood you but I actually think you meant to say:

"the fall-out of a decision not to make a 'transaction' around a
_'take'_ operation."

i.e.  The original problem is caused by an errant outstanding take not a
write.

That said, if you're doing multiple writes you might want to wrap them
all up in a transaction to make sure you get "all or none".  Of course,
JavaSpace05 introduces a bulk write operation which would achieve the
same thing in some cases without a transaction.  However, in other cases
a transaction would still be required to bundle up the bulk write with
other operations (perhaps including takes).

> I doff my cap to you, gentlemen!
>

Thank you!

Dan.

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html

JDC members can download the JavaSpaces(tm) Technology from:
http://developer.java.sun.com/developer/products/jini/