I just released Slash-Client, which right now is useful only for one thing: talking to Slash sites with SOAP to do journal stuff. I've been using it to post journals for a few weeks.
The base Slash::Client module handles authentication and SOAP stuff, while Slash::Client::Journal is merely a frontend to the SOAP calls add_entry, modify_entry, delete_entry, get_entry, and get_entries.
Read up on authentication in the Slash::Client POD, see the example in t/journal.t, and everything else should be self-explanatory.
Have fun. Let me know if you've got any problems.
Now Playing: Johnny Cash - Hurt
Net::Blogger... (Score:1)
Re:Net::Blogger... (Score:2)
Re:Net::Blogger... (Score:1)
At the very least, I need to take a look at what you have an see how to make Net::Bloggers Slash support better.
Re:Net::Blogger... (Score:2)
It's code I use anyway, and I will support it as I make changes to Slash::Journal itself, and over time it will offer other client functions beyond journals.
Prosumeably they do the same thing. Was there something broken that I need to fix?
As I don't know your code at all, I couldn't say.
Re:Net::Blogger... (Score:1)
As I don't know your code at all, I couldn't say.
Neither do I yet. :-) As soon as I get maintanership of N::B and have a look at your API, maybe I can reverse the roles so N::B uses your client. It would certainly mean it will stay more up to date with the API that way.
Are you using SOAP or SOAPLite?
Re:Net::Blogger... (Score:2)