seqeron 0.18.0
Loading...
Searching...
No Matches
Session.cs File Reference

Classes

class  Org.Limitless.Seqeron.App.Session
 What every seqeron client does the same way: the cluster session it submits on, the co-located queue it follows, confirmed ingress across a failover, and the fences that say when it may no longer act — wired together into one DoWork whose ordering is not the caller's to get right.
 
interface  Org.Limitless.Seqeron.App.Session.IDispatch
 What the façade above does with what comes off the queue, and with a fence.
 

Namespaces

namespace  Org
 
namespace  Org.Limitless
 
namespace  Org.Limitless.Seqeron
 
namespace  Org.Limitless.Seqeron.App
 

Typedefs

using Replay = Org.Limitless.Seqeron.Sbe.Replay
 
using SbeBuffer = Org.SbeTool.Sbe.Dll.DirectBuffer
 

Typedef Documentation

◆ Replay

using Replay = Org.Limitless.Seqeron.Sbe.Replay

◆ SbeBuffer

using SbeBuffer = Org.SbeTool.Sbe.Dll.DirectBuffer