TLSessioning can be used for basic Session Joining. Session Joining is the joining of fragments into a single fragment.
For example, the hits below represent two different physical sessions, as determined by TLTSID:
Hit 1: TLTSID = C70C0F4F451ED57190F8D5A059A1D071 Hit 2: TLTSID = C70C0F4F451ED57190F8D5A059A1D071 Hit 3: TLTSID = C70C0F4F451ED57190F8D5A059A1D071 User-Key = 20E8AB8F-531D Hit 4: TLTSID = C70C0F4F451ED57190F8D5A059A1D071 User-Key = 20E8AB8F-531D Hit 5: TLTSID = 649B0BDA4BC15E0B141AD99791282A13 User-Key = 20E8AB8F-531D Hit 6: TLTSID = 649B0BDA4BC15E0B141AD99791282A13 User-Key = 20E8AB8F-531D Hit 7: TLTSID = 649B0BDA4BC15E0B141AD99791282A13
To combine these fragments into a single session, hits 5-7 should have the same TLTSID as hits 1-4. The configuration is as follows:
PrimarySessField=TLTSID PrimaryLooseStrict=Strict PrimaryMaxFieldLen=36 SecondarySessField=User-Key SecondaryLooseStrict=Strict SecondaryMaxFieldLen=20
When Hit3 is processed, TLSessioning notes the presence of
User-Key and associates the SessionID (in this case,
C70C0F4F451ED57190F8D5A059A1D071) with it. When Hit5 arrives, the TLTSID changes, indicating the start of a new session. While this TLTSID is appearing for the first time, TLSessioning already associates the User-Key value to an existing TLTSID, so the first identifier (
C70C0F4F451ED57190F8D5A059A1D071) replaces the new TLTSID.
This User-Key value is also associated with the new TLTSID. When Hit7 is processed without a User-Key value, TLSessioning can continue to associate the correct TLTSID with this hit.