Quote:
there is no separate method to read the session data. Tough using data() method, data read is possible, I think there should be also need a data_read() method to just read session data.Noneed for a seperate routine IMO - just use:
my $data = $ses->data();
It's clear and concise.
Quote:
no correct method, to check existance of a session.You shouldn't need to check the existance except when loading the session file, which is when you create a new session object anyway and so can check for errors. If you already have a session object then that means the session is valid, otherwise new() would have returned an error.
Quote:
The recommended way by doc is, to set directory path using this code: However it is bad, since creates new session file, which will be not used for anything.
Did you try this out?...it doesn't actually create a new redundant session file. If you pass in id => $id then it loads the existing session file and updates the directory path at the same time.
Quote:
One more bug: When printing out the session object using Dumper for debugging reasons, I see that the 'directory' value is missing, even if was previously set by $GT::Session::File::DIRECTORY = $sessions_path; code.Mmm no it's not a bug, if you are priting out the session object, then of course $DIRECTORY won't be shown because it's not part of the object, it's a global scalar.
Quote:
Did anybody else face such problems with GT::Session::File?No.
