Assembly: GemStone.GemFire.Cache (in GemStone.GemFire.Cache.dll) Version: 188.8.131.52
public void Put( CacheableKey key, Serializable value, IGFSerializable callback )
Public Sub Put ( _ key As CacheableKey, _ value As Serializable, _ callback As IGFSerializable _ )
public: void Put( CacheableKey^ key, Serializable^ value, IGFSerializable^ callback )
- Type: GemStone.GemFire.Cache CacheableKey
a key object associated with the value to be put into this region.
- Type: GemStone.GemFire.Cache Serializable
the value to be put into this region
- Type: GemStone.GemFire.Cache IGFSerializable
argument that is passed to the callback functions
|GemStone.GemFire.Cache IllegalArgumentException||if key is null|
|GemStone.GemFire.Cache CacheWriterException||if CacheWriter aborts the operation|
|GemStone.GemFire.Cache CacheListenerException||if CacheListener throws an exception|
|GemStone.GemFire.Cache RegionDestroyedException||if region has been destroyed|
|GemStone.GemFire.Cache CacheServerException||If an exception is received from the Java cache server. Only for Native Client regions.|
|GemStone.GemFire.Cache NotConnectedException||if not connected to the GemFire system because the client cannot establish usable connections to any of the servers given to it. For pools configured with locators, if no locators are available, innerException of NotConnectedException is set to NoAvailableLocatorsException.|
|GemStone.GemFire.Cache TimeoutException||if the operation timed out|
|GemStone.GemFire.Cache OutOfMemoryException||if there is not enough memory for the value|
If there is already an entry associated with the specified key in this region, the entry's previous value is overwritten. The new put value is propogated to the java server to which it is connected with. Put is intended for very simple caching situations. In general it is better to create a ICacheLoader object and allow the cache to manage the creation and loading of objects.
If remote server put fails throwing back a CacheServerException or security exception, then local put is tried to rollback. However, if the entry has overflowed/evicted/expired then the rollback is aborted since it may be due to a more recent notification or update by another thread.