Secondly, I'd like to suggest that the documentation for the checkfriends protocol mode be changed slightly. Currently, the client is asked to supply an empty string for lastupdate once per session, and the string specified by LiveJournal each time thereafter. However, clients should also probably specify a blank string for lastupdate after the user acknowledges an update, otherwise if there's more than one update before the user acknowledges them and loads their webbrowser, the server will erronously say that the page has been updated again immediately after the user acknowledges the original update and resumes their client.
GKLJ 0.1.0 / comment on protocol
Secondly, I'd like to suggest that the documentation for the checkfriends protocol mode be changed slightly. Currently, the client is asked to supply an empty string for lastupdate once per session, and the string specified by LiveJournal each time thereafter. However, clients should also probably specify a blank string for lastupdate after the user acknowledges an update, otherwise if there's more than one update before the user acknowledges them and loads their webbrowser, the server will erronously say that the page has been updated again immediately after the user acknowledges the original update and resumes their client.
-
"Invalid password" when calling login method over XML-RPC
A week or two ago my LJBackup client started being unable to login - I didn't change anything (I think!), but now I always get an "Invalid password"…
-
cl-journal livejournal client
Hey everyone, I'd like to present a livejournal client that I wrote to fulfill my needs but maybe there are other people that can find it…
-
SessionGenerate and ljloggedin
Are there any information after release 86 and changes in cookies scheme to use sessiongenerate? It returns ljsession key, but this key is not enough…
- Post a new comment
- 1 comment
- Post a new comment
- 1 comment
