Log in

No account? Create an account
LiveJournal Client Discussions [entries|archive|friends|userinfo]
LiveJournal Client Discussions

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

persistent client login / selective updating? [Jun. 28th, 2005|03:46 pm]
LiveJournal Client Discussions


I'm trying to hack together a little Perl script to do mass tag updates, and would like to get it to work without having to go through the challenge/response bit for every single update (or at least every 60s). But the 'login' response doesn't set a cookie, so I can't use the cookie method to log in after that... is there any way to use challenge/response to log in once, and have it set a cookie for subsequent logins? Or is there another method that would give me a cookie?

On another note, as the client/server docs don't have much on tags yet, is there any way to get and/or update -just- the tags of a specific entry, without having to grab or send back the entire entry along with it? Since export.bml doesn't give you the tags, I have to grab the whole entry to update the tags list, which is a bit of a waste (suppose there's always 'truncate 4'..). And, as I've confirmed on a tests entry, sending just the taglist w/o the event & everything else will delete the entry- any way around that, or is it always necessary to re-send everything?

[User Picture]From: hyuri
2005-06-29 01:40 am (UTC)
Check out sessiongenerate. And don’t forget to kill the cookie with sessionexpire!

And, in case you’re wondering, it does work in flat.
(Reply) (Thread)
[User Picture]From: threeleet
2005-06-29 01:48 am (UTC)
Duh, didn't even notice those. Thanks!
(Reply) (Parent) (Thread)
(Deleted comment)
(Deleted comment)
(Deleted comment)
[User Picture]From: threeleet
2005-06-29 08:54 pm (UTC)
What I'm doing is grepping through an offline backup to find entries to tag, but since those don't export the tags yet, I have to grab the entry to get them (i.e. if they already have tags, I need to add to the list instead of just sending 1 new tag). For the update, I can either use 'prefersubject=1' to grab the tags & then use the 'event' from the archive, which would save a little bandwidth, or just grab the whole entry & pass it back with the modified taglist, which would ensure that the most current version stays there (in case the archive isn't completely up to date). Could always make that an option, I suppose..
(Reply) (Parent) (Thread)