http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/system-statistics/operating_system_statistics.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/system-statistics/operating_system_statistics.html.md.erb b/geode-docs/nativeclient/system-statistics/operating_system_statistics.html.md.erb deleted file mode 100644 index eec64a8..0000000 --- a/geode-docs/nativeclient/system-statistics/operating_system_statistics.html.md.erb +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Operating System Statistics ---- - -Use operating system statistics to determine a memberâs CPU, memory, and disk usage. - -- **[Linux Process Statistics](../../nativeclient/system-statistics/linux_os_statistics.html)** - - Use these methods to get information about a Linux operating system process that is using a GemFire system. - -- **[Solaris Process Statistics](../../nativeclient/system-statistics/solaris_os_statistics.html)** - - Use these methods to get information about a Solaris operating system process that is using a GemFire system - -- **[Windows Process Statistics](../../nativeclient/system-statistics/windows_os_statistics.html)** - - Use these methods to get information about a Windows operating system process that is using a GemFire system. - -
http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/system-statistics/pool_statistics.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/system-statistics/pool_statistics.html.md.erb b/geode-docs/nativeclient/system-statistics/pool_statistics.html.md.erb deleted file mode 100644 index cc51aa4..0000000 --- a/geode-docs/nativeclient/system-statistics/pool_statistics.html.md.erb +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Pool Statistics ---- - -Use the pool object to get statistics on connection pools. - -| | | -|-------------------------------|---------------------------------------------------------------------------------------------------------------| -| `locators` | Current number of locators discovered. | -| `servers` | Current number of servers discovered. | -| `locatorRequests` | Number of requests from this connection pool to a locator. | -| `locatorResponses` | Number of responses from the locator to this connection pool. | -| `poolConnections` | Current number of pool connections. | -| `connects` | Total number of times a connection has been created. | -| `ConnectionWaitTime` | Total time (nanoseconds) spent waiting for a connection. | -| `disconnects` | Total number of times a connection has been destroyed. | -| `minPoolSizeConnect` | Total number of connects done to maintain minimum pool size. | -| `loadConditioningConnects` | Total number of connects done due to load conditioning. | -| `idleDisconnects` | Total number of disconnects done due to idle expiration. | -| `loadConditioningDisconnects` | Total number of disconnects done due to load conditioning expiration. | -| `connectionWaitsInProgress` | Current number of threads waiting for a connection. | -| `connectionWaits` | Total number of times a thread completed waiting for a connection (by timing out or by getting a connection). | -| `clientOpsInProgress` | Current number of clientOps being executed. | -| `clientOps` | Total number of clientOps completed successfully. | -| `clientOpFailures` | Total number of clientOp attempts that have failed. | -| `clientOpTimeouts` | Total number of clientOp attempts that have timed out. | -| `QueryExecutions` | Total number of queryExecutions. | -| `QueryExecutionTime` | Total time spent while processing queryExecution. | - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/system-statistics/region_statistics.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/system-statistics/region_statistics.html.md.erb b/geode-docs/nativeclient/system-statistics/region_statistics.html.md.erb deleted file mode 100644 index 4df1fae..0000000 --- a/geode-docs/nativeclient/system-statistics/region_statistics.html.md.erb +++ /dev/null @@ -1,113 +0,0 @@ ---- -title: Region Statistics ---- - -These methods help you to get the statistics of a region. - -<a id="concept_7AA863080074439286F4F51048BC2159__section_8A343C8D6425469DA314D9A96E543A24"></a> -<table> -<colgroup> -<col width="50%" /> -<col width="50%" /> -</colgroup> -<tbody> -<tr class="odd"> -<td><code class="ph codeph">creates</code></td> -<td>Total number of cache creates for this region.</td> -</tr> -<tr class="even"> -<td><code class="ph codeph">puts</code></td> -<td>Total number of cache put operations for this region.</td> -</tr> -<tr class="odd"> -<td><code class="ph codeph">putTime</code></td> -<td>Total time spent doing put operations for this region.</td> -</tr> -<tr class="even"> -<td><code class="ph codeph">putAll</code></td> -<td>Total number of cache putAlls for this region.</td> -</tr> -<tr class="odd"> -<td><code class="ph codeph">putAllTime</code></td> -<td>Total time spent doing putAll operations for this region.</td> -</tr> -<tr class="even"> -<td><code class="ph codeph">gets</code></td> -<td>Total number of cache gets for this region.</td> -</tr> -<tr class="odd"> -<td><code class="ph codeph">getTime</code></td> -<td><p>Total time spent doing get operations for this region.</p></td> -</tr> -<tr class="even"> -<td><code class="ph codeph">getAll</code></td> -<td>Total number of cache getAlls for this region.</td> -</tr> -<tr class="odd"> -<td><code class="ph codeph">getAllTime</code></td> -<td>Total time spent doing getAll operations for this region.</td> -</tr> -<tr class="even"> -<td><code class="ph codeph">hits</code></td> -<td>Total number of cache hits for this region.</td> -</tr> -<tr class="odd"> -<td><code class="ph codeph">misses</code></td> -<td>Total number of cache misses for this region.</td> -</tr> -<tr class="even"> -<td><code class="ph codeph">entries</code></td> -<td>Current number of cache entries for this region.</td> -</tr> -<tr class="odd"> -<td><code class="ph codeph">destroys</code></td> -<td>Total number of cache destroys for this region.</td> -</tr> -<tr class="even"> -<td><code class="ph codeph">clears</code></td> -<td>Total number of cache clears for this region.</td> -</tr> -<tr class="odd"> -<td><code class="ph codeph">overflows</code></td> -<td>Total number of cache overflows to disk for this region.</td> -</tr> -<tr class="even"> -<td><code class="ph codeph">retrieves</code></td> -<td>Total number of cache entries fetched from disk into the cache region.</td> -</tr> -<tr class="odd"> -<td><code class="ph codeph">nonSingleHopCount</code></td> -<td>Total number of times client request required multiple hops.</td> -</tr> -<tr class="even"> -<td><code class="ph codeph">metaDataRefreshCount</code></td> -<td>Total number of times metadata was refreshed due to the observation of multiple hops.</td> -</tr> -<tr class="odd"> -<td><code class="ph codeph">cacheLoaderCallCompleted</code></td> -<td>Total number of times a load has completed for this region.</td> -</tr> -<tr class="even"> -<td><code class="ph codeph">cacheLoaderCallTime</code></td> -<td>Total time spent invoking the loaders for this region.</td> -</tr> -<tr class="odd"> -<td><code class="ph codeph">CacheWriterCallsCompleted</code></td> -<td>Total number of times a cache writer call has completed for this region.</td> -</tr> -<tr class="even"> -<td><code class="ph codeph">CacheWriterCallTime</code></td> -<td>Total time spent doing cache writer calls.</td> -</tr> -<tr class="odd"> -<td><code class="ph codeph">CacheListenerCallsCompleted</code></td> -<td>Total number of times a cache listener call has completed for this region.</td> -</tr> -<tr class="even"> -<td><code class="ph codeph">CacheListenerCallTime</code></td> -<td>Total time spent doing cache listener calls for this region.</td> -</tr> -</tbody> -</table> - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/system-statistics/sampling_statistics.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/system-statistics/sampling_statistics.html.md.erb b/geode-docs/nativeclient/system-statistics/sampling_statistics.html.md.erb deleted file mode 100644 index f8f4b68..0000000 --- a/geode-docs/nativeclient/system-statistics/sampling_statistics.html.md.erb +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Sampling Statistics ---- - -When applications and cache servers join a distributed system, they indicate whether to enable statistics sampling and whether to archive the statistics that are gathered. - -The following statistics are related to the statistic sampler. - -| | | -|---------------|------------------------------------------------| -| `sampleCount` | Total number of samples taken by this sampler. | -| `sampleTime` | Total amount of time spent taking samples. | -| `StatSampler` | Statistics on the statistic sampler. | - -For more information about configuring statistics, see [Attributes in gfcpp.properties](../setting-properties/attributes-gfcpp.html#attributes-gfcpp). - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/system-statistics/solaris_os_statistics.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/system-statistics/solaris_os_statistics.html.md.erb b/geode-docs/nativeclient/system-statistics/solaris_os_statistics.html.md.erb deleted file mode 100644 index 4b19b37..0000000 --- a/geode-docs/nativeclient/system-statistics/solaris_os_statistics.html.md.erb +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Solaris Process Statistics ---- - -Use these methods to get information about a Solaris operating system process that is using a Geode system. - -| | | -|-------------------|----------------------------------------------------------------------| -| `imageSize` | Size of the process image in megabytes. | -| `rssSize` | Size of the process resident set in megabytes. | -| `userTime` | Operating system statistic for the process CPU usage in user time. | -| `systemTime` | Operating system statistic for the process CPU usage in system time. | -| `processCpuUsage` | Operating system statistic for the CPU usage of this process. | -| `hostCpuUsage` | Operating system statistic for the host CPU usage. | -| `threads` | Number of threads currently active in this process. | - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/system-statistics/system_performance_statistics.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/system-statistics/system_performance_statistics.html.md.erb b/geode-docs/nativeclient/system-statistics/system_performance_statistics.html.md.erb deleted file mode 100644 index b7d69e6..0000000 --- a/geode-docs/nativeclient/system-statistics/system_performance_statistics.html.md.erb +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: System Performance Statistics ---- - -Performance statistics are collected for each application or cache server that connects to a distributed system. - -- **[Region Statistics](../../nativeclient/system-statistics/region_statistics.html)** - - These methods help you to get the statistics of a region. - -- **[Cache Performance Statistics](../../nativeclient/system-statistics/cache_performance_statistics.html)** - - Use cache performance statistics to determine the type and number of cache operations being performed and how much time they consume. - -- **[Continuous Query Statistics](../../nativeclient/system-statistics/continuous_query_statistics.html)** - - Continuous query statistics give you information about a registered Continuous Query (CQ) represented by the CqQuery object. - -- **[CQ Service Statistics](../../nativeclient/system-statistics/cq_service_statistics.html)** - - Use CQ service methods to get aggregate statistical information about the continuous queries of a client. - -- **[Pool Statistics](../../nativeclient/system-statistics/pool_statistics.html)** - - Use the pool object to get statistics on connection pools. - -- **[Delta Statistics](../../nativeclient/system-statistics/delta_statistics.html)** - - Delta statistics provide information about updates to data. - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/system-statistics/windows_os_statistics.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/system-statistics/windows_os_statistics.html.md.erb b/geode-docs/nativeclient/system-statistics/windows_os_statistics.html.md.erb deleted file mode 100644 index f247cd9..0000000 --- a/geode-docs/nativeclient/system-statistics/windows_os_statistics.html.md.erb +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Windows Process Statistics ---- - -Use these methods to get information about a Windows operating system process that is using a Geode system. - -| | | -|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `handles` | Total number of handles currently open by this process. This number is the sum of the handles currently open by each thread in this process. | -| `priorityBase` | Current base priority of the process. Threads within a process can raise and lower their own base priority relative to the process's base priority. | -| `threads` | Number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread. | -| `activeTime` | Elapsed time in milliseconds that all threads of this process used the processor to execute instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count. | -| `pageFaults` | Total number of page faults by the threads executing in this process. A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This will not cause the page to be fetched from disk if it is on the standby list and hence already in main memory, or if it is in use by another process with whom the page is shared. | -| `pageFileSize` | Current number of bytes this process has used in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and lack of space in paging files can prevent other processes from allocating memory. | -| `pageFileSizePeak` | Maximum number of bytes this process has used in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and lack of space in paging files can prevent other processes from allocating memory. | -| `privateSize` | Current number of bytes this process has allocated that cannot be shared with other processes. | -| `systemTime` | Elapsed time in milliseconds that the threads of the process have spent executing code in privileged mode. When a Windows system service is called, the service often runs in Privileged Mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. These subsystem processes provide additional protection. Therefore, some work done by Windows on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process. | -| `userTime` | Elapsed time in milliseconds that this process's threads have spent executing code in user mode. Applications, environment subsystems, and integral subsystems execute in user mode. Code executing in User Mode cannot damage the integrity of the Windows Executive, Kernel, and device drivers. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. These subsystem processes provide additional protection. Therefore, some work done by Windows on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process. | -| `virtualSize` | Current size in bytes of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite, and by using too much, the process can limit its ability to load libraries. | -| `virtualSizePeak` | Maximum number of bytes of virtual address space the process has used at any one time. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is however finite, and by using too much, the process might limit its ability to load libraries. | -| `workingSetSize` | Current number of bytes in the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If pages are needed, they are then soft-faulted back into the Working Set before they are paged out to disk. | -| `workingSetSizePeak` | Maximum number of bytes in the Working Set of this process at any point in time. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft faulted back into the Working Set before they leave main memory. | -| `cpuUsage` | Percentage CPU used by this process. | -| `WindowsProcessStats` | Statistics for a Microsoft Windows process. | - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/transactions/how-native-client-xacts-work.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/transactions/how-native-client-xacts-work.html.md.erb b/geode-docs/nativeclient/transactions/how-native-client-xacts-work.html.md.erb deleted file mode 100644 index f7104a4..0000000 --- a/geode-docs/nativeclient/transactions/how-native-client-xacts-work.html.md.erb +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: How Native Client Transactions Work ---- - -The syntax for writing client transactions is the same as with server or peer transactions, but when a client performs a transaction, the transaction is delegated to a server that brokers the transaction. - -## <a id="how-native-client-xacts-work__section_C804F1FE5BDF49CEA037AA589BBF284E" class="no-quick-link"></a>Role of Server Delegates in Transactions - -The Geode native client can run transactions on the Java cache server, using a server delegate to actually run the transaction code. - -For information on transaction requirements and activities on the server side, see [Transactions](../../developing/transactions/chapter_overview.html). - -**Note:** -The client cache blocks until the transaction is successfully committed. However, the client cache block is removed if the transaction is suspended. - -Depending on where the data resides, the server transaction delegate may or not be the same member that hosts the transaction. This is the same as for transactions run by the servers, but for server-run transactions, there is no delegate. There is just the member that is directly running its own transaction code. - -In this figure, the application code on the client makes changes to data entries Y and Z within a transaction. The server delegate that performs the transaction, M1, does not host the primary copy of the data being modified. The transaction takes place on server M2, where the data resides. - -<a id="how-native-client-xacts-work__fig_7E408D84E18C452683077528756E31C3"></a> -<span class="figtitleprefix">Figure: </span>Transaction Run From a Client - -<img src="../common/images/xact-run-from-client.gif" id="how-native-client-xacts-work__image_E9ED33166A994014942ABAD9E6F61755" class="image" /> - -To maintain cache consistency, the local client cache is not accessible during a transaction as it may reflect information inconsistent with the transaction in progress. When the transaction completes, the local cache is accessible again. - -In addition to the failure conditions common to all transactions, client transactions can also fail if the transaction delegate fails. If the delegate performing the transaction fails, the transaction code throws a `TransactionException`. - -## <a id="how-native-client-xacts-work__section_434BA87403C1449FADC3E7796E30F3C7" class="no-quick-link"></a>Native Client Transaction APIs - -The Geode API for distributed transactions has the familiar relational database methods, `begin`, `commit`, and `rollback`. There are also APIs available to suspend and resume transactions. - -The .NET classes for executing transactions are: - -**GemStone::GemFire::Cache::Generic** - -- CacheTransactionManager -- TransactionId - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/transactions/running-native-client-xact.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/transactions/running-native-client-xact.html.md.erb b/geode-docs/nativeclient/transactions/running-native-client-xact.html.md.erb deleted file mode 100644 index 879b1cc..0000000 --- a/geode-docs/nativeclient/transactions/running-native-client-xact.html.md.erb +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Running a Native Client Transaction ---- - -Before you can run a native client transaction, you must configure your clients and servers; define your server regions for your transactions; and define your client regions. - -1. Retrieve the Geode cache transaction manager. - - **C++ example** - - ``` pre - CacheTransactionManagerPtr txManager = - cache->getCacheTransactionManager(); - ``` - - **C\# .NET example** - - ``` pre - CacheTransactionManager txManager = - cache.CacheTransactionManager; - ``` - -2. Run your transaction. (Detailed steps follow the examples.) - - **C++ example** - - ``` pre - TransactionIdPtr tid; - txManager->begin(); - // ..do work - tid = txManager->suspend(); - // following code can be run from another - // thread that has access to tid - try { - txManager->resume(tid); - // ..do work - tid = txManager->commit(); - } catch (const CommitConflictException& e) { - // ..on exception - } - ``` - - **C\# .NET example** - - ``` pre - TransactionId tid; - txManager.Begin(); - // ..do work - tid = txManager.Suspend(); - // following code can be run from another - // thread that has access to tid - try { - txManager.Resume(tid); - // ..do work - txManager.Commit(); - } catch (CommitConflictException e) - ``` - - Start each transaction with a `begin` operation. - - If your transaction runs on server regions that are a mix of partitioned and replicated regions, perform your first transaction operation on a partitioned region. This sets the server data host for the entire transaction. If you are using PR single-hop, single-hop will be applied as usual to this first operation. - - Run the Geode operations and other operations that you want included in the transaction. - - End each transaction with a `commit` or a `rollback`. - **Note:** - Do not leave any transaction in an uncommitted and unrolled back state unless you have suspended the transaction. Transactions that have not been explicitly suspended do not time out, so will remain in the system for the life of your application. - -3. Review all of your client code for compatibility with transactions. - -When you commit a transaction, while the commit is taking place, the changes are visible in the cache. This is also known as transition commits. This provides better performance than locking everything to do the transaction updates, but it means that another process accessing data used in the transaction might get some data in the pre-transaction state and some in the post-transaction state. - -For example, keys 1 and 2 are written to in a transaction so both of their values change from A to B. In another thread, it is possible to read key 1 with value B and key 2 with value A, while the transaction is being committed. This can happen because of how Geode performs reads. This choice sacrifices atomic visibility in favor of performance. Reads do not block writes. Writes do not block reads. - -Because the client cache waits during transaction execution, and client regions are not distributed, the only activities that interact with a client transaction are those that occur on the server. - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/transactions/suspend-resume-xacts.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/transactions/suspend-resume-xacts.html.md.erb b/geode-docs/nativeclient/transactions/suspend-resume-xacts.html.md.erb deleted file mode 100644 index 64d7915..0000000 --- a/geode-docs/nativeclient/transactions/suspend-resume-xacts.html.md.erb +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Suspending and Resuming Transactions ---- - -The ability to suspend and resume transactions is useful when a thread must perform operations that should not be part of the transaction before the transaction can complete. - -When a transaction is suspended, it loses the transactional view of the cache. None of the previous operations (before calling suspend) are visible to the thread. Subsequently any operations that are performed by the thread do not participate in the suspended transaction. - -When a transaction is resumed, the resuming thread assumes the transactional view. A transaction that is suspending on a member must be resumed on the same member. Before resuming a transaction, you may want to check if the transaction exists on the member and whether it is suspended. You may optionally use the `tryResume` method. - -If the member with the primary copy of the data crashes, the transactional view that applied to that data is lost. The secondary member for the data cannot resume transactions suspended on the crashed member. You need to take remedial steps to retry the transaction on a new primary copy of the data. - -If a suspended transaction is not touched for a period of time, Geode cleans it up automatically. By default, the timeout for a suspended transaction is 30 minutes and can be configured by using the `suspended-tx-timeout` property of the `gfcpp.properties` file. The suspended transaction timeout value is specified in milliseconds. - -See [Running a Native Client Transaction](running-native-client-xact.html) for code examples of how to suspend and resume a transaction. - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/transactions/transactions.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/transactions/transactions.html.md.erb b/geode-docs/nativeclient/transactions/transactions.html.md.erb deleted file mode 100644 index 9d40356..0000000 --- a/geode-docs/nativeclient/transactions/transactions.html.md.erb +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Transactions ---- - -*Transactions* describes how transactions work on the client side. It provides examples for running, suspending, and resuming transactions. - -Geode client transactions run on the server tier. The client uses a server delegate that runs the transaction as it would a local transaction. Thus, the key to running client transactions lies in making sure the server is properly configured and programmed. For complete information about Geode transactions in the Java server, see [Transactions](../../developing/transactions/chapter_overview.html). It provides detailed information including server data requirements, interactions of Geode transactions with other operations running on the server tier, server-side application plug-ins with transactions, and querying with transactions. - -- **[How Native Client Transactions Work](../../nativeclient/transactions/how-native-client-xacts-work.html)** - - The syntax for writing client transactions is the same as with server or peer transactions, but when a client performs a transaction, the transaction is delegated to a server that brokers the transaction. - -- **[Running a Native Client Transaction](../../nativeclient/transactions/running-native-client-xact.html)** - - Before you can run a native client transaction, you must configure your clients and servers; define your server regions for your transactions; and define your client regions. - -- **[Suspending and Resuming Transactions](../../nativeclient/transactions/suspend-resume-xacts.html)** - - The ability to suspend and resume transactions is useful when a thread must perform operations that should not be part of the transaction before the transaction can complete. - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/type_mappings/chapter_overview.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/type_mappings/chapter_overview.html.md.erb b/geode-docs/nativeclient/type_mappings/chapter_overview.html.md.erb deleted file mode 100644 index fbb15ac..0000000 --- a/geode-docs/nativeclient/type_mappings/chapter_overview.html.md.erb +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Interoperability of Language Classes and Types ---- - -*Interoperability of Language Classes and Types* provides a table that maps C++ class methods to corresponding .NET class methods and a table that maps Java types to .NET types. - -- **[C++ Class to .NET Class Mappings](../../nativeclient/type_mappings/cpp-class-to-dotnet-class-mappings.html)** - -- **[Java to .NET Type Mapping Table](../../nativeclient/type_mappings/java-to-dotnet-type-mapping.html)** - - - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/type_mappings/cpp-class-to-dotnet-class-mappings.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/type_mappings/cpp-class-to-dotnet-class-mappings.html.md.erb b/geode-docs/nativeclient/type_mappings/cpp-class-to-dotnet-class-mappings.html.md.erb deleted file mode 100644 index 366154e..0000000 --- a/geode-docs/nativeclient/type_mappings/cpp-class-to-dotnet-class-mappings.html.md.erb +++ /dev/null @@ -1,169 +0,0 @@ ---- -title: C++ Class to .NET Class Mappings ---- - -Wherever the native C++ class methods use pass-by-reference semantics to return data, the corresponding .NET methods shown in the following table return the object instead of using pass-by-reference semantics. - -<a id="concept_FD847E19497C4985ACB247C0FA2C2AD5__table_8D8D228E223E4E89A313A17DB5C38652"></a> - -<table> -<caption><span class="tablecap">Table 1. C++ Class to .NET Class Mappings</span></caption> -<colgroup> -<col width="50%" /> -<col width="50%" /> -</colgroup> -<thead> -<tr class="header"> -<th><p>C++ Class</p></th> -<th><p>.NET Class</p></th> -</tr> -</thead> -<tbody> -<tr class="odd"> -<td>class <code class="ph codeph">gemfire::AttributesFactory</code></td> -<td>Sealed class <code class="ph codeph">AttributesFactory</code></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire::AttributesMutator</code></p></td> -<td>Sealed class <code class="ph codeph">AttributesMutator</code></td> -</tr> -<tr class="odd"> -<td>class <code class="ph codeph">gemfire::Cache</code></td> -<td>Sealed class <code class="ph codeph">Cache</code></td> -</tr> -<tr class="even"> -<td><p>abstract class <code class="ph codeph">gemfire:: Cacheable</code></p></td> -<td><p>Interface <code class="ph codeph">IPdxSerializable</code> or interface <code class="ph codeph">IGFSerializable</code></p></td> -</tr> -<tr class="odd"> -<td><p>class <code class="ph codeph">gemfire::CacheableBytes</code></p></td> -<td><p><code class="ph codeph">Byte[]</code> or <code class="ph codeph">ArrayList<Byte></code></p></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire::Cacheableint32</code></p></td> -<td><p><code class="ph codeph">Int32</code></p></td> -</tr> -<tr class="odd"> -<td><p>class <code class="ph codeph">gemfire:: CacheableString</code></p></td> -<td><p><code class="ph codeph">String</code></p></td> -</tr> -<tr class="even"> -<td><p>abstract class <code class="ph codeph">gemfire:: CacheableKey</code></p></td> -<td><p>You can use any type that implements <code class="ph codeph">hashcode</code> and <code class="ph codeph">equals</code>. The generic .NET built-in types are all suitable.</p></td> -</tr> -<tr class="odd"> -<td><p>abstract class <code class="ph codeph">gemfire::CacheListener</code></p></td> -<td><p>Interface <code class="ph codeph">ICacheListener</code></p></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire:: CacheLoader</code></p></td> -<td><p>Interface <code class="ph codeph">ICacheLoader</code> plus static class <code class="ph codeph">CacheLoader</code></p></td> -</tr> -<tr class="odd"> -<td><p>class <code class="ph codeph">gemfire:: CacheWriter</code></p></td> -<td><p>Interface class <code class="ph codeph">ICacheWriter</code></p></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire::CacheFactory</code></p></td> -<td><p>Sealed class <code class="ph codeph">CacheFactory</code></p></td> -</tr> -<tr class="odd"> -<td><p>class <code class="ph codeph">gemfire::DataInput</code></p></td> -<td><p>With <code class="ph codeph">IPdxSerializable</code>, <code class="ph codeph">IPdxReader.</code></p> -<p>With <code class="ph codeph">IGFSerializable</code>, sealed class <code class="ph codeph">DataInput</code>.</p></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire:: DataOutput</code></p></td> -<td><p>With <code class="ph codeph">IPdxSerializable</code>, <code class="ph codeph">IPdxWriter.</code></p> -<p>With <code class="ph codeph">IGFSerializable</code>, sealed class <code class="ph codeph">DataOutput</code>.</p></td> -</tr> -<tr class="odd"> -<td><p>class <code class="ph codeph">gemfire:: DiskPolicyType</code></p></td> -<td><p>enum <code class="ph codeph">DiskPolicyType</code> plus static class <code class="ph codeph">DiskPolicy</code> containing convenience methods for <code class="ph codeph">DiskPolicyType</code> enumeration</p></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire:: DistributedSystem</code></p></td> -<td><p>Sealed class <code class="ph codeph">DistributedSystem</code></p></td> -</tr> -<tr class="odd"> -<td><p>class <code class="ph codeph">gemfire:: EntryEvent</code></p></td> -<td><p>Sealed class <code class="ph codeph">EntryEvent</code></p></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire:: Exception</code></p></td> -<td><p>Class <code class="ph codeph">GemfireException</code></p></td> -</tr> -<tr class="odd"> -<td><p>all other exceptions deriving from <code class="ph codeph">gemfire:: Exception</code></p></td> -<td><p>Corresponding exceptions deriving from <code class="ph codeph">GemfireException</code></p></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire:: ExpirationAction</code></p></td> -<td><p>enum <code class="ph codeph">ExpirationAction</code> plus static class <code class="ph codeph">Expiration</code> containing convenience methods for <code class="ph codeph">ExpirationAction</code> enumeration</p></td> -</tr> -<tr class="odd"> -<td><p>class <code class="ph codeph">gemfire:: Log</code></p></td> -<td><p>Static class <code class="ph codeph">Log</code>. The native <code class="ph codeph">Log::log</code> method is mapped to <code class="ph codeph">Log.Write</code> to avoid the conflict with the class name which is reserved for the constructors of Log class. The various loglevel <code class="ph codeph">Throw</code> or <code class="ph codeph">Catch</code> methods are not implemented, since they are redundant to <code class="ph codeph">Log::Log</code> , <code class="ph codeph">Log::LogThrow</code>, and <code class="ph codeph">Log::LogCatch</code> methods that take <code class="ph codeph">LogLevel</code> as a parameter.</p></td> -</tr> -<tr class="even"> -<td><p>enum <code class="ph codeph">gemfire:: MemberType</code></p></td> -<td><p>enum <code class="ph codeph">MemberType</code></p></td> -</tr> -<tr class="odd"> -<td><p>abstract class <code class="ph codeph">gemfire:: PersistanceManager</code></p></td> -<td><p>Not provided. You can register a C++ implementation using <code class="ph codeph">AttributesFactory.SetPersistenceManager</code> but you cannot implement a new one in .NET</p></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire:: Properties</code></p></td> -<td><p>Sealed class <code class="ph codeph">Properties</code></p></td> -</tr> -<tr class="odd"> -<td><p>class <code class="ph codeph">gemfire:: Properties::Visitor</code></p></td> -<td><p>Delegate <code class="ph codeph">PropertiesVisitor</code></p></td> -</tr> -<tr class="even"> -<td><p>abstract class <code class="ph codeph">gemfire:: Region</code></p></td> -<td><p>Class <code class="ph codeph">IRegion</code></p></td> -</tr> -<tr class="odd"> -<td><p>class <code class="ph codeph">gemfire:: RegionAttributes</code></p></td> -<td><p>Sealed class <code class="ph codeph">RegionAttributes</code></p></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire:: ScopeType</code></p></td> -<td><p>enum <code class="ph codeph">ScopeType</code> plus static class <code class="ph codeph">Scope</code> containing convenience methods for <code class="ph codeph">ScopeType</code> enumeration+</p></td> -</tr> -<tr class="odd"> -<td><p>abstract class <code class="ph codeph">gemfire:: Serializable</code></p></td> -<td><p>Two options:</p> -<ul> -<li><p>Interface <code class="ph codeph">IPdxSerializable</code></p></li> -<li><p>Interface <code class="ph codeph">IGFSerializable</code> plus wrapper <code class="ph codeph">Serializable</code> class for native <code class="ph codeph">Serializable</code> and <code class="ph codeph">UserData</code> objects. The native <code class="ph codeph">toString</code> method is not provided, since the <code class="ph codeph">ToString</code> method of the base object class provides the same functionality.</p></li> -</ul></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire:: SystemProperties</code></p></td> -<td><p>Sealed class <code class="ph codeph">SystemProperties</code></p></td> -</tr> -<tr class="odd"> -<td><p>class <code class="ph codeph">gemfire:: UserData</code></p></td> -<td><p>Two options:</p> -<ul> -<li><p>Interface <code class="ph codeph">IPdxSerializable</code></p></li> -<li><p>Interface <code class="ph codeph">IGFSerializable</code></p></li> -</ul></td> -</tr> -<tr class="even"> -<td><p>class <code class="ph codeph">gemfire:: VectorT<T></code></p></td> -<td><p>Array of the given type, such as T[]</p></td> -</tr> -</tbody> -</table> - -: <span class="tablecap">Table 1. C++ Class to .NET Class Mappings</span> - -- **[Interoperability of C++ Types When Using PDX Serialization](../../nativeclient/cpp-caching-api/type_interoperability.html)** - - This topic table lists the mapping between C++ types and other language types when using PDX serialization. - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/de0559be/geode-docs/nativeclient/type_mappings/java-to-dotnet-type-mapping.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/nativeclient/type_mappings/java-to-dotnet-type-mapping.html.md.erb b/geode-docs/nativeclient/type_mappings/java-to-dotnet-type-mapping.html.md.erb deleted file mode 100644 index 9eff179..0000000 --- a/geode-docs/nativeclient/type_mappings/java-to-dotnet-type-mapping.html.md.erb +++ /dev/null @@ -1,147 +0,0 @@ ---- -title: Java to .NET Type Mapping Table ---- - -The following table provides a mapping between Java and .NET types. - -<a id="concept_24D0AAC71FF1483AB47A7772DA018966__table_F85EC7AA1E1140E9888B753E812E65E4"></a> - -<table> -<caption><span class="tablecap">Table 1. Java types and .NET types</span></caption> -<colgroup> -<col width="50%" /> -<col width="50%" /> -</colgroup> -<thead> -<tr class="header"> -<th>Java Type</th> -<th>.NET Type</th> -</tr> -</thead> -<tbody> -<tr class="odd"> -<td><p>instances of <code class="ph codeph">PdxSerializable</code></p></td> -<td><p>.NET class of same name</p></td> -</tr> -<tr class="even"> -<td><p>instances of <code class="ph codeph">PdxInstance</code></p></td> -<td><p>.NET class of same name</p></td> -</tr> -<tr class="odd"> -<td><p>instances serialized by a <code class="ph codeph">PdxSerializer</code></p></td> -<td><p>.NET class of same name</p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">java.lang.Byte </code></p></td> -<td><p><code class="ph codeph">System.SByte </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">java.lang.Boolean </code></p></td> -<td><p><code class="ph codeph">System.Boolean </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">java.lang.Character </code></p></td> -<td><p><code class="ph codeph">System.Char </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">java.lang.Short </code></p></td> -<td><p><code class="ph codeph">System.Int16 </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">java.lang.Integer </code></p></td> -<td><p><code class="ph codeph">System.Int32 </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">java.lang.Long </code></p></td> -<td><p><code class="ph codeph">System.Int64 </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">java.lang.Float </code></p></td> -<td><p><code class="ph codeph">System.Float </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">java.lang.Double </code></p></td> -<td><p><code class="ph codeph">System.Double </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">java.lang.String </code></p></td> -<td><p><code class="ph codeph">System.String </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">java.util.Date </code></p></td> -<td><p><code class="ph codeph">System.DateTime </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">byte[] </code></p></td> -<td><p><code class="ph codeph">System.Byte[] </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">boolean[] </code></p></td> -<td><p><code class="ph codeph">System.Boolean[] </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">char[] </code></p></td> -<td><p><code class="ph codeph">System.Char[] </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">short[] </code></p></td> -<td><p><code class="ph codeph">System.Int16[] </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">int[] </code></p></td> -<td><p><code class="ph codeph">System.Int32[] </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">long[] </code></p></td> -<td><p><code class="ph codeph">System.Int64[] </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">float[] </code></p></td> -<td><p><code class="ph codeph">System.Float[] </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">double[] </code></p></td> -<td><p><code class="ph codeph">System.Double[] </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">String[] </code></p></td> -<td><p><code class="ph codeph">System.String[] </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">byte[][] </code></p></td> -<td><p><code class="ph codeph">System.Byte[][] </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">Object[] </code></p></td> -<td><p><code class="ph codeph">system.Collections.Generic.List<Object> </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">java.util.HashMap </code></p></td> -<td><p><code class="ph codeph">System.Collections.Generics.IDictionary<Object, Object> </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">java.util.Hashtable </code></p></td> -<td><p><code class="ph codeph">System.Collections.Hashtable </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">java.util.ArrayList </code></p></td> -<td><p><code class="ph codeph">System.Collections.Generic.IList<Object> </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">java.util.Vector </code></p></td> -<td><p><code class="ph codeph">Collections.ArrayList </code></p></td> -</tr> -<tr class="odd"> -<td><p><code class="ph codeph">java.util.HashSet </code></p></td> -<td><p><code class="ph codeph">CacheableHashSet </code></p></td> -</tr> -<tr class="even"> -<td><p><code class="ph codeph">java.util.LinkedHashSet </code></p></td> -<td><p><code class="ph codeph">CacheableLinkedHashSet </code></p></td> -</tr> -</tbody> -</table> - -<span class="tablecap">**Table 1.** Java types and .NET types</span> - -
