Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Feature Request: Consistent interface for IMap and TransactionalMap #8729
In creating code that will conditionally need to operate on data in Hazelcast, I noticed that the two classes IMap and TransactionalMap have different methods, and don't have a consistent interface for the more advanced functions. For example, I have to use code such as the following:
If these various calls had a single interface, it would make mixed transactional/non-transactional code much easier to deal with.