You need to sign in to do that
Don't have an account?
rjk
New Perl implementation: Sforce::Sfdc
I have packaged up version 0.03 of my new Perl implementation for Sforce, which I have named Sforce::Sfdc. My company is releasing this code as free software under the LGPL.
Sforce::Sfdc inherits from XMLRPC::Lite, and was based on the code posted here by Ron Hess. It is object-oriented and should be both platform-independent and interface-independent.
http://www.focalex.com/sforce/Sforce-Sfdc-0.03.tar.gz
Please download the module, check it out, and give me feedback. I'm especially looking for feedback on the following issues:
1) The name of the module. Maybe it should be XML::Sforce, or Sforce::XMLRPC, or...
2) Anything I did that is bad practice in terms of XML and XML-RPC. I have very little experience in that area.
3) The interface for the helper methods, e.g. login(username => $username, password => $password). Should I just make that login($username, $password)? What about the more complicated methods, such as query()?
4) Bugs, of course.
5) Features that would be useful to have.
I'll post the current documentation as a reply to this message.
enjoy!
Ronald
Sforce::Sfdc inherits from XMLRPC::Lite, and was based on the code posted here by Ron Hess. It is object-oriented and should be both platform-independent and interface-independent.
http://www.focalex.com/sforce/Sforce-Sfdc-0.03.tar.gz
Please download the module, check it out, and give me feedback. I'm especially looking for feedback on the following issues:
1) The name of the module. Maybe it should be XML::Sforce, or Sforce::XMLRPC, or...
2) Anything I did that is bad practice in terms of XML and XML-RPC. I have very little experience in that area.
3) The interface for the helper methods, e.g. login(username => $username, password => $password). Should I just make that login($username, $password)? What about the more complicated methods, such as query()?
4) Bugs, of course.
5) Features that would be useful to have.
I'll post the current documentation as a reply to this message.
enjoy!
Ronald
Very cool, this is a big improvement, and well written doc too !
the naming looks fine, I will port some of my nightly jobs over to this module and let you know what i run into.
Thanks !.
Thanks a million! This is just what I've been looking for. Dropped it in and it worked without any trouble. I've now implemented a few things with it and am very pleased. A couple of comments fyi and a question:
1. In my application I save the session_id and server_url between instances. To tell the module to use the old ones (instead of logging in again), I do:
$sfdc->{'session_id'} = $sid;
$sfdc->{'server_url'} = $URL;
This works fine, of course, but isn't explicitly endorsed by the docs...
2. I removed the prepending of "Response error" to error strings so that I could just get back the raw sforce error message.
3. More general question: Is access of sforce through XMLRPC here to stay, or will things be migrating in the SOAP direction in the future?
Thanks again for posting this. It's been very helpful.
- Nicholas
1. I had no idea that would work. I'm not sure the module should explicitly support it, but it won't explicitly prevent it either.
2. I can take out the prepending to error strings if that's not useful.
Also, I realized the error string doesn't include the fault code; I think I'll add a $err variable for that.
3. Uh oh, I don't know. I guess it wouldn't be too hard to convert this module to use SOAP instead of XML-RPC, if that happens.