Excellent work alt! Where did you find the info for the websocket interface, from reading the code?
I'm just starting to design a BitShares authentication plugin for the Joomla CMS, and was going to use the standard RPC interface to the BitShares client. That will work, but since I'm starting from scratch it may make more sense to utilize the new websockets I/F.
I basically just need to validate a BitShares account name and perhaps later I'll get into obtaining account balances or other info to facilitate shopping cart transactions. If you could point me to any info about the websocket I/F I would greatly appreciate it.
Here are my initial thoughts:
Basic BitShares authentication scheme for JoomlaNOTE:
the credentials of Joomla and BitShares use separate passwords but share the account name. A Joomla account must be created with its own password. The common binding is the Joomla username == a valid, authenticated BitShares account name. This avoids sending wallet password across the Internet, and allows for normal Joomla authentication without BitShares but provides an isolated integration of the BitShares ecosystem if the BitShares wallet is active and unlocked. Prerequisite
| Joomla server side
)1) User starts the BitShares wallet (either GUI or CMD Line version).
2) User interacts with BitShares (opens and unlocks the wallet or just logs into GUI).
3) User clicks the "login" link on Joomla website.
8 ) If the credentials are rejected the joomla BitShares plugin cascades down to the next active joomla auth plugin (if any). If there are no other auth methods configured, an "authentication failed" error message is displayed to user.