Session ID tightly coupled with the framework

[kunalyadavdfe]

Environment - Flexibility: session ID tightly coupled with the framework. De-coupling would make the Framework more extensible.
Session ID storage – This was found to be in a configuration file rather than using industry standards making the framework less extensible. Changes to this will have to be done by us for our needs but such tight coupling should again be avoided where possible

[iantasker]

@rafidzal Do you have any current plans to move the session ID from the settings file to a DB field?

[rafidzal]

By default, the SIF Framework provides a simple implementation for the management of session IDs through the ISessionService interface. The current implementation uses the configuration file purely for the sake of convenience and to simplify the provided demo projects. It is expected that for an enterprise-level solution, developers implement their own session service and update the SessionsManager class (until such time as a DI framework can be incorporated). The documentation will be enhanced to better explain how this can be achieved.