?

Log in

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

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

introduction and a question [Apr. 2nd, 2004|04:11 pm]
LiveJournal Client Discussions

lj_clients

[ryptide]
Hello all.

New member here. I found this group while looking for a php interface to livejournal. I was planning on building one so that I can easily syndicate my main weblog to livejournal whenever I update the main weblog. I got tired long ago of copy/pasting to update both, and my content on LJ has suffered because of it

Before I get started developing a tool, I wanted to see what else is out there. I'm basically looking for something to accept user, password, subject, event and possibly mood and music that will create a post on lj. I would include this in my cms application to update livejournal whenever I update the weblog. My weblog is home-rolled, so I'm not looking for any sort of MT or Blogger plugin.

I haven't gone through all of the archives yet, just the most recent pages, and I haven't seen anything that jumped right out at me.

Can anyone point me in the right direction?

Thanks!
linkReply

Comments:
[User Picture]From: ryptide
2004-04-02 01:44 pm (UTC)
I'm looking at this now as well.

you have to add that support to php though, correct? I'm not sure my host has that enabled.

I don't see --with-xmlrpc in my phpinfo().
(Reply) (Parent) (Thread)
[User Picture]From: vanbeast
2004-04-02 01:46 pm (UTC)
Yeah, that's right. It doesn't require any external libraries, though, so my guess would be they'd be happy to add it in if you asked.
(Reply) (Parent) (Thread)
[User Picture]From: ryptide
2004-04-02 01:49 pm (UTC)
I'll ask them.

Thanks.

What about the flat interface? Could I use that?
(Reply) (Parent) (Thread)
[User Picture]From: vanbeast
2004-04-02 01:51 pm (UTC)
You *could* use the flat interface, but it's going to be a lot more complex. You'll have to do raw requests and parse them blah blah blah. XML-RPC is the future.

One thing I remembered after I made my comment is that there are existing pure-PHP XML-RPC implementations... that is, classes you can use that don't require the extension. It's likely better to try to get your host to set it up for you, though.

I believe http://phpxmlrpc.sourceforge.net/ is one such implementation. There are others, I'm sure, and this one may not be the best, it's just the first I found from casual googling.
(Reply) (Parent) (Thread)
[User Picture]From: benzado
2004-04-02 01:53 pm (UTC)

flat

flat is just a regular HTTP POST (try making a web form with /interface/flat as the action) so it is probably even easier to do from PHP. Especially if you only want to push posts and not retrieve any data.
(Reply) (Parent) (Thread)
[User Picture]From: vanbeast
2004-04-02 01:59 pm (UTC)

Re: flat

The XML-RPC is exactly the same, it's just a POST to /interface/xmlrpc

The difference is how you encode the data and decode the results.
(Reply) (Parent) (Thread)
[User Picture]From: ryptide
2004-04-02 02:02 pm (UTC)

Re: flat

All I'm doing is adding/updating/deleting data. I'm not pulling it down to display anything.
(Reply) (Parent) (Thread)
[User Picture]From: vanbeast
2004-04-02 02:11 pm (UTC)

Re: flat

Well, you might be better off with the flat then. I'm a big proponent of completeness and re-usability, so if I were in your position I'd attempt to develop a generic access layer and then interface your program with it. But that's just me.

At the very least, you're going to want to check for success or failure, and I still think it'll be easier with XML-RPC :)
(Reply) (Parent) (Thread)
[User Picture]From: ryptide
2004-04-02 02:12 pm (UTC)

Re: flat

Absolutely. I'm really *not* looking for the easy way out.

I just wanted to see if someone had already developed something so I'm not reinventing the wheel here.

I'd rather use XMLRPC as well, and I'm talking with my host about it's availability.
(Reply) (Parent) (Thread)