Hello.
This is both a query about the session and login mechanism for automated logins to the secondlife.com site and an enquiry about transaction API features being considered / feature request.
There are a handful of residents, like myself, that run web-sites connected to in-world services that involve financial transactions.
Due to the lack of a status return from the llPay() LSL function, we've all been forced to implement back-end server mechanisms for periodically automatically logging into the secondlife.com site via HTTP/SSL,downloading the transaction logs and parsing them.
Prior to the last web-site update, the system I had in place for that worked fine. It connects to the site via HTTP/SSL, POSTs the login form, fetches the transactions download with appropriate date parameters and parses the result.
In order for that to work, it retreives and re-sends the session cookie "PHPSESSID".
However, since the last web-update, that mechanism stopped working. An inspection of the returned headers from the login pages shows a new "second-life-member" cookie that contains the avatar key and other detail.
Thus far, I've been updable to implement a sucessful login even using this cookie - though that is no doubt a bug on my end - but it brings me to ask these questions:
* Are there any plans to make a simpler web-service API for retrieval of the transaction logs?
* Alternatively, is a transaction notification mechanism being considered?
- for example, entries could be sent via email (either one-by-one or in batches), similar to the way offline-IM notifications come (perhaps with an alternative email, if possible).
- or alternatively, via HTTP POST or even XMLRPC requests to an external server we can specify?
That would greatly simplify the lives of operators of 3rd-party sites such as myself.
Thank you,
-Cenji.
http://www.apez.biz