I haven't read your post in full (I appologize) but you may want to read
http://bytemaster.bitshares.org/article/2014/12/22/BitShares-Login/
If you haven't already
@xeroc:
I don't recall that post in BM's blog, but I have been in contact with gamey about the SMF login.
From my quick perusal and gamey's into the SMF side is not well structured, so it's difficult to understand the client / server flow of things.
I took a quick look at the code, but haven't gotten around to ask gamey for the user's use case scenario. Perhaps BM's blog will provide that. I do know that gamey's implementation was based on Oauth somewhere, perhaps only as a starting point.
I'll (re)read BM's blog on it. I'm pretty sure I read it back in December, but I'm not sure.
@alt:
if the new websocket (not webService) I/F is not in the current 0.9.2 release yet, then how are you doing this? Do you have inside access to the private code base the dev team is working on now before the release? And if it is out now, my original question stands, how did you figure out how to use it, by looking at the code or some other way?
Since you published the src code I could look at it and try to reverse engineer it, but that is prone to mistakes and is far more difficult (in most cases) than talking to the author (or reading API docs if they exist).
Your original post mentioned both "web socket" and rpc, tho I took that to mean a generic use of rpc. Then xeroc said it was the first public use of the new websocket I/F, and you didn't correct him. Thus my presumption is based on that.
I see you're using python & flask, which I have some (limited) familiarity with, since wackou's bts_tools is based on that stack as well, coupled with the ngnix webserver. Low overhead, fast response.