[sync] SyncML session problem

[Anthony Mills]

I don't think we can use Horde authentication methods.  I mean we use 
them, but we can not use the session information that goes with it.  I 
don't know how to send the SyncML client the session id created 
automagicly.  So in the method getStateFromSession, I create a new 
session with a new session id, and this seems to work fine.  The second 
http request does not create the a new state, it uses the one out of the 
session.  The values I change in state don't seem to persist, but the 
object does.  This where I run into trouble.

Anthony

Jan Schneider wrote:

> Zitat von Anthony Mills <amills at gascard.net>:
>
>> Most of the code should be in the correct place and in the correct
>> order.  The main problem I seem to be having is with State.  The State
>> variable is stored in $_SESSION['SyncML.state'], but it will not retain
>> the state across multiple http requests.  This is probably my fault, I
>> think it is the mutable/immutable problem.  If you look at |function
>> getStateFromSession($sourceURI, $locName, $sessionID) on line 166 of
>> SyncML.php, we create the session, and the session does persist.  We do
>> not have to create a new State on the next request.  The problem is the
>> isAuthorized is false.  It was true on the last request. I may not be
>> updating the State in |$_SESSION['SyncML.state']| correctly.  Does
>> anyone know what I could be doing wrong?
>
>
> You probably overwrite/delete/whatever the horde session (where
> authentication details are stored) with your sync session.
> If you use Horde's auth mechanisms, you already *have* a session that you
> can use and don't need to create your own one.
>
> Jan.
>
> -- 
> http://www.horde.org - The Horde Project
> http://www.ammma.de - Neue Wege des Lernens
> http://www.tip4all.de - Deine private Tippgemeinschaft