Skip to content

Conversation

@olegz
Copy link
Contributor

@olegz olegz commented Nov 8, 2011

No description provided.

@markfisher
Copy link
Contributor

A couple comments/questions which would also apply in hindsight to the master branch version of these changes.

  1. should we actually store Lock objects (ReadWrite) and replace the simple synchronized blocks with lock acquisition and release calls?
  2. If the answer to Touched an inappropriate file #1 is NO, then as a minor naming thing, I would probably call the current "locks" just "monitors" since that's the role they are playing
  3. I might also simplify the 'groupIdToMessageGroup' name to just 'groupMap' or even 'groups' since using the group ID as the key seems intuitive enough that such detail is not needed in the name of the map.

@olegz
Copy link
Contributor Author

olegz commented Nov 10, 2011

This is only about SimpleMessageStore (in memory) so I am not sure what do you mean when you say 'store Lock objects' os I say NO.

Yes I agree with renaming

@markfisher
Copy link
Contributor

I was talking about java.util.concurrent.locks.ReadWriteLock, which is precisely for in-VM. If synchronized blocks are sufficient, then fine, but ReadWriteLocks are obviously more versatile.

@markfisher
Copy link
Contributor

It looks like you did not synch your local 'maint' branch before creating this one on top of it.

@olegz
Copy link
Contributor Author

olegz commented Nov 10, 2011

Try now

@markfisher markfisher closed this Nov 10, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants