[jira] Created: (RIVER-53) Lease spec does not talk about thread safety

["Jim Waldo (JIRA)" <ji...@apache.org>]

Lease spec does not talk about thread safety
--------------------------------------------

                 Key: RIVER-53
                 URL: https://issues.apache.org/jira/browse/RIVER-53
             Project: River
          Issue Type: Improvement
          Components: net_jini_lease
    Affects Versions: jtsk_2.1
            Reporter: Jim Waldo
            Priority: Minor


Currently the lease spec does not comment on the thread safety of Leases
or LeaseMaps. Probably makes sense to be explicit one way or another.

Note, this bug is not trying to address the question of whether or not
a service's implementation is renew and/or cancel is thread
safe/coherent. Such a requirement would have far reaching implications
is probably best dealt with on a service spec by service spec basis.

Leases logically have two pieces of local state, the expiration and
the serialization format. The spec could require access to and
mutation of the expiration to be thread safe, while allowing the
format to be non-thread safe. This may be acceptable because the usage
models of the format are much more limited and should be easer for a
client to impose thread safety from the outside. Additionally, in
those cases where a client is likely to have a problem the client will
need to impose external serialization anyway - even if the Lease is
completely thread safe. It may be desirable because requiring access to
and mutation of the expiration to be thread safe complicates
serialization of Leases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.