Enums.FeatureServiceSessionType enumeration

  • QML Enumeration List
  • Enums.FeatureServiceSessionType enumeration
  • Session types—transient and persistent—let you control how multiple viewers and editors access branch versioned feature services. By default, a web map or web scene with branch versioned feature services (a ServiceGeodatabase version) loads as a Enums.FeatureServiceSessionTypeTransient type; you can change this type to Enums.FeatureServiceSessionTypePersistent at the map or scene level when you load the map or scene.

    When you switch the ServiceGeodatabase version being used via ServiceGeodatabase::switchVersion(string), a read operation is started on the new version before releasing the previous version. If acquiring a shared lock on the new version fails (for example, if another user is editing the version), an error is raised. This behavior allows you to keep the user connected to the original version when the version they want is not yet available.

    For additional ways to manage multiple viewers and editors in branch versioned data, such as using multiple tiers of editors, see the ArcGIS Pro discussion on branch version scenarios.

    The FeatureServiceSessionType can be one of:

    Enums.FeatureServiceSessionTypeTransient(0) A momentary session is used during queries and edit operations. This is the default session type. The server creates an exclusive lock upon an editor's ServiceGeodatabase::applyEdits operation and holds the lock only for the duration that it takes that operation to occur. An exclusive lock prevents readers and editors from accessing (connecting to and viewing) the rows affected by the edit in the ServiceGeodatabase version during this time, but they can access (connect to, view, query, and edit) other rows in the ServiceGeodatabase version. Use the transient type when concurrency is more important than data consistency between queries or between concurrent users.
    Enums.FeatureServiceSessionTypePersistent(1) A session is held open as long as tables are actively reading or writing.

    If one or more read operations were already being performed on the ServiceFeatureTable when an edit operation began (if a shared lock was already in place), then the shared lock becomes an exclusive lock. When all edit operations are applied successfully, the exclusive lock returns to being a shared lock.

    A call to ServiceGeodatabase::close will release an exclusive lock.

    Note that if the ServiceGeodatabase version requested is the default version, no exclusive lock will be acquired.

    Edit operations that trigger the locks described above:

    Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.