I agree with you, however unfortunately the phpbb_session class currently has a lot of procedures that deal with many sessions. ```session_gc``` is one example.

I think you are right, but splitting session's responsibilities up to a class that deals with only one sessions, and a class that deals with many sessions might have to be a separate focus. Currently I am just focusing on separating out the underlying storage. Moving these calls to the session class is essential to achieving this, and will help in the goal to split up session's responsibilities in the future.