Log in

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

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

The Lemming save us from bad documentation and people who talk at the theatre [Aug. 8th, 2007|12:57 pm]
LiveJournal Client Discussions


I've been set a programming exercise of creating a fully-featured class to communicate with LJ servers, using both the flat and XML-RPC APIs. Problem is that the LJ documentation appears to be woefully out of date. Would anyone happen to have an up-to-date copy of the flat and XML-RPC API docs, or failing that, a list of everything that's different in implementation from the docs, including missing functions? Any information on possible differences/traps between LJ's in-use code base and their open source code base would be useful, too.

[User Picture]From: ralesk
2007-08-08 10:21 am (UTC)

One I can instantly remember is that you get a flat status='OK' from the server even on a wrong password.

(Reply) (Thread)
[User Picture]From: ralesk
2007-08-08 10:28 am (UTC)

Sending an unknown prop results in an error instead of getting ignored or resulting in a warning sent back — this makes it especially fun to support LiveJournal and GreatestJournal (the latter not having Location prop) at the same time. We can’t ask the server for capabilities, so we have to build a database of our own and hope it’s good.

I think I also have some other issues and discrepancies documented in my source or my changelog of ljKlient, I don’t remember more off the top of my head however.

(Reply) (Thread)
[User Picture]From: vertelemming
2007-08-08 05:40 pm (UTC)
Thanks! Digging through the source of your client has given me most of the information I need for the flat interface component, and most of it should be fairly easy to implement. It's a bit annoying about GJ not supporting the Location prop, and LJ not seeming to use its protocol versioning at all in the API, but I'll manage.

Now I just need to work out the XML-RPC. It seems to mostly match the flat API, but it's still going to be "fun".
(Reply) (Parent) (Thread)