Darryl L. Pierce wrote: > +++ Michael DeHaan [13/08/08 15:31 -0400]: >> You may want to add calling to check_token() (or is it >> "token_check"?) prior to token usage, or at least test what happens >> when the token expires. I'm not sure if the code is doing that or >> not, but I thought I would point it out. >> >> Not logging in repeatedly would be a good thing -- it produces extra >> log entries and depending on what you are authing against, may incur >> some lag. > > I was thinking about how to handle checks for that but wasn't sure of > a good > path. One way would be to, on a writable call, retry a failed call > once by > assuming the auth_token had expired.
That is probably not optimal.... You could probably pay attention to the fault string that is returned. XMLRPC faults don't have different types, but you can detect the one who's message is login failure related. > It all depends on how seamless the need for a log should be. If the > framework > doesn't bother trying to hide it, then an expired auth_token will just > result > in a failed attempt to update the Cobbler server. But, if we try to > handle it > then we take on a heck of a task. > I don't think it will be that bad. Cobbler's WUI itself handles this and makes you log in again, IIRC. > Ideas? The above, probably. > > ------------------------------------------------------------------------ > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
