[jira] [Updated] (UNOMI-744) Consider session ID creation on Unomi side instead of client applications side.

["Kevan Jahanshahi (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/UNOMI-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevan Jahanshahi updated UNOMI-744:
-----------------------------------
    Summary: Consider session ID creation on Unomi side instead of client applications side.  (was: Consider session ID creation on Unomi side instead of client side.)

> Consider session ID creation on Unomi side instead of client applications side.
> -------------------------------------------------------------------------------
>
>                 Key: UNOMI-744
>                 URL: https://issues.apache.org/jira/browse/UNOMI-744
>             Project: Apache Unomi
>          Issue Type: Improvement
>    Affects Versions: unomi-2.1.0
>            Reporter: Kevan Jahanshahi
>            Priority: Major
>
> Proposal is:
>  * Add new option(s) on Context endpoint to request a new *sessionID* (mean client won't have to provide the {*}sessionID{*})
>  * Unomi could generate the *sessionID* using format:
>  ** UUID-indexName, like: UUID-000001, UUID-000002
>  * Then Unomi would return the *sessionID* in the context response.
> This would provide two major improvements:
>  * {*}improve performance on first visitor /context requests and response time{*}. As we know that session doesn't exists and should be new, so we don't have to ask if session exists or not like today.
>  * *improve session/index affinity* for nexts incoming /context requests, that would increase session retrieval consistency in case of index rolling over.
> To be consider:
>  * this could be a breaking changes for client side applications that are generating the session IDs on there side



--
This message was sent by Atlassian Jira
(v8.20.10#820010)