"EnTerr" wrote:
I said '''no separate "* Edit blah" buttons next to the fields'''. You can use the buttons as text fields. There is no need to have 2 different entities side to side. Buttons already have a label inside.
"ioan" wrote:
I'm sure you are right and everything could be done with roUrlTransfer, but for me it was easier to use roStreamSocket. I'm not sure how would m-jpeg or rtsp be implemented with roUrlTransfer, but I know how to do it with roStreamSocket. How do you continuously read packets into a roByteArray from the socket using roUrlTransfer?
"EnTerr" wrote:"ioan" wrote:
I'm sure you are right and everything could be done with roUrlTransfer, but for me it was easier to use roStreamSocket. I'm not sure how would m-jpeg or rtsp be implemented with roUrlTransfer, but I know how to do it with roStreamSocket. How do you continuously read packets into a roByteArray from the socket using roUrlTransfer?
Oh, that! Running an "infinite" download for mjpeg or rtsp. I got nothing on that with roUrlXfer.
But: I disabled any authentication on the Dlink camera and even the simplest /image.jpg still does not work - which to me points at the difficulties of implementing right http protocol when doing it from scratch.
PS. wait - "no authentication" is supported, right?! what authentications are supported currently?
"ioan" wrote:
Majority of cameras with mjpeg stream work (with or without basic authentication) right now. D-Link cameras seem like are sending a realm challenge even without authentication and that's not supported just yet. I found a d-link camera online with open access and looked the wireshark capture shows exactly that.
if left(path, 1) <> "/" then path = "/" + path
if path.instr("?") < 0 then path = path + "?"
"EnTerr" wrote:"ioan" wrote:
Majority of cameras with mjpeg stream work (with or without basic authentication) right now. D-Link cameras seem like are sending a realm challenge even without authentication and that's not supported just yet. I found a d-link camera online with open access and looked the wireshark capture shows exactly that.
No, that's not it! :lol:
I just figured it out on my end - apparently it's really, really, REALLY important (WTF?) to type the URL end with a "?" - and i was not doing that because why would you do an empty query when there are no params^. And it was not working. But by accident i read the help text of the web interface and it's stressing to append "?" and prepend "/" - so i tried that and now it works - at least the "/image.jpg?". With and without authentication! And so i ran here to take back my words but too late.
Here is a radical proposal - do not rely what people type will start with "/" and end with "?" - just check if that's the case and "fix" it otherwise:
if left(path, 1) <> "/" then path = "/" + path
if path.instr("?") < 0 then path = path + "?"
(^) in retrospect, now i can divine you are slapping a cache-buster param behind
"ioan" wrote:
I guess not all D-Link cameras have problems, but for example this one has: http://82.209.221.91:8080/2.mjpg?997267910[/url:2ni6nri5] which supposedly is a D-Link. The check f...
< Server: Boa/0.94.14rc21Could be Vivotek, Zavio, TP-Link (somewhat random results from a search).
< WWW-Authenticate: Basic realm="streaming_server"
"EnTerr" wrote:"ioan" wrote:
I guess not all D-Link cameras have problems, but for example this one has: http://82.209.221.91:8080/2.mjpg?997267910[/url:2oyg1b7a] which supposedly is a D-Link. The check f...
It doesn't sound like a D-link:< Server: Boa/0.94.14rc21
< WWW-Authenticate: Basic realm="streaming_server"
Could be Vivotek, Zavio, TP-Link (somewhat random results from a search).
"ioan" wrote:"EnTerr" wrote:
Could be Vivotek, Zavio, TP-Link (somewhat random results from a search).
You are somewhere on the West Coast, right? I'm in Salem Oregon.
"EnTerr" wrote:"ioan" wrote:"EnTerr" wrote:
Could be Vivotek, Zavio, TP-Link (somewhat random results from a search).
You are somewhere on the West Coast, right? I'm in Salem Oregon.
Yes... how, ummm, does this relate?