There should be a close session to release the SID cookie at one point, yes. There currently isn't. All searches work on the same cookie which was returned after the first authentication. The benefit of this method is: there is not another authentication needed for every search.
The real question is thus: At what step to do a close session? After each search? (safest method, most overhead) After Bibdesk Quits? (not needed, next startup will get you a new SID cookie) After the search returns a "session timeout"? (yes, for sure) Reto On Mar 30, 2014, at 12:36 AM, Adam R. Maxwell wrote: > > On Mar 29, 2014, at 15:32 , Christiaan Hofman <[email protected]> wrote: > >> Another thing about the WOK search. Shouldn't there be a closeSession to >> balance the authentication? >> >> I am not completely sure whether we can actually do that. Perhaps it can be >> done from serverDidFinish, but I am not sure if that works and is save, as >> it does a soap operation, though that does run its own run loop. > > That seems like a reasonable place to do it; I don't see any way to do it > earlier, and it would be running on the background thread. It looks like that > would be sent to the singleton +[WOKMWSAuthenticateService > WOKMWSAuthenticateServiceSoapBinding]? > > -- > Adam > > ------------------------------------------------------------------------------ > _______________________________________________ > Bibdesk-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop ------------------------------------------------------------------------------ _______________________________________________ Bibdesk-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
