Thread Rating:
  • 2 Votes - 3 Average
  • 1
  • 2
  • 3
  • 4
  • 5
OhNet.SoapRequest [OhNet JS API]
06-07-2011, 01:41 PM
Post: #1
OhNet.SoapRequest [OhNet JS API]
Where would I find details for OhNet.SoapRequest*? I can see plenty of code calling it (Via the Doxygen comments here [http://www.openhome.org/build/nightly/docs/Js/) but they are all related to the Proxys themselves, not the lower level OhNet JS API.

Rik

* & indeed the while OhNet JS API - let me know if you need any help with the JS code - Konductor is 95% JS & is full of stuff which looks very familiar / similar.
Find all posts by this user
06-07-2011, 02:41 PM
Post: #2
RE: OhNet.SoapRequest [OhNet JS API]
Hi Rik,

The documentation for OhNet.SoapRequest will be available soon. In the meantime, what you can do is get the code from git and look at the comments within the source.

If you haven't done so, the instructions to acquire the ohNet source is on http://www.openhome.org/wiki/Ohnet-How.

OhNet.SoapRequest is located at ohNet\Upnp\Public\Js\WebUIsdk\ProxyCore.js

Cheers

Chris
Find all posts by this user
06-07-2011, 02:44 PM (This post was last modified: 06-07-2011 03:14 PM by rik.)
Post: #3
RE: OhNet.SoapRequest [OhNet JS API]
Thanks Chris, I'll take a look.

Rik
Hi,

A quick look at the code. I notice you're using "console.log" which implies running in a browser, not necessarily something like node.js or under Rhino etc. Could be useful to make this parameterisable. Also btoa & atob are extensions but I guess as top-level objects I can easily override - could do the same with console.log I guess but it belays a (I would guess false) impression of browser based API.

Good stuff though - these a just my nit pickings.

Rik
Yep - very good stuff.

You've certainly been doing your homework.

Thanks for sharing,

Rik
Find all posts by this user
06-07-2011, 04:21 PM
Post: #4
RE: OhNet.SoapRequest [OhNet JS API]
Hi Rik,

Thanks for the feedback.

At the moment, we have been targeting browser based control points.
I agree that the code implies a browser based API.
This is something we would like to look at in future revisions.

If you wish, you are very welcome to submit patches. (PM for further info)

Many Thanks

Chris
Find all posts by this user


Forum Jump: