Hi folks !<br clear="all">
<br><br><div class="gmail_quote">2011/7/23 Steffen Gebert <span dir="ltr"><<a href="mailto:steffen.gebert@typo3.org">steffen.gebert@typo3.org</a>></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
You can push your change into a sandbox:<br>
<br>
git push origin HEAD:sandbox/<username>/<<u></u>branchname></blockquote><div>Thank you for the tip.</div><div><br></div><div>I "pushed" into HEAD:sandbox/popy/t3lib_session. It contains the t3lib_session class, which is near complete.</div>
<div><br></div><div>Please note that :</div><div>- IPlock is not implemented yet</div><div>- I didn't start any rewrite into t3lib_userauth</div><div>- It probably lack a garbage collector</div><div>- time() calls should maybe be replaced by some SIM_EXEC_TIME</div>
<div>- I choosed to check session expiration on php side in order to be able to re-use expired session record (instead of deleting it and recreating a new one)</div><div>- this system is totally independant of "user's" things. That session is linked to the browser, not to the Xe_user, and could (should) remain after login/logout</div>
<div><br></div><div>I think that special keys in sessionData could be used to separate backend/frontend/anonymous sessions (FE_id, FE_ses, BE_id, BE_ses and PUBLIC_ses for instance)</div></div><br><div>Regards</div><div>Pierre Dudoret, AKA Popy</div>