Difference between revisions of "Talk:Change API legacy"
From ElphelWiki
| Line 1: | Line 1: | ||
This doesn't seem to work, at least on the 353 series... 404 error. | This doesn't seem to work, at least on the 353 series... 404 error. | ||
Does the 353 even do the AxisAPI?--[[User:Bnewbold|Bnewbold]] 21:39, 30 May 2007 (CDT) | Does the 353 even do the AxisAPI?--[[User:Bnewbold|Bnewbold]] 21:39, 30 May 2007 (CDT) | ||
| + | |||
| + | |||
| + | No, it does not. I'm working on adding access to all of the internal features from php (currently there are too many IOCTL-s used), with that it will be possible to implement custom API with just PHP - it seems to work nicely in fastcgi mode with lighttpd. | ||
| + | |||
| + | Temporary there are two web servers running in the camera - port 80 - boa, port 81 - lighttpd (seems to be some 20% faster). You may try | ||
| + | http://192.168.0.7/phpinfo.php (boa, php in cgi mode) and | ||
| + | http://192.168.0.7:81/phpinfo.php (lighttpd, php in fastcgi mode) | ||
| + | --[[User:Andrey.filippov|Andrey.filippov]] 02:30, 31 May 2007 (CDT) | ||
Revision as of 23:30, 30 May 2007
This doesn't seem to work, at least on the 353 series... 404 error. Does the 353 even do the AxisAPI?--Bnewbold 21:39, 30 May 2007 (CDT)
No, it does not. I'm working on adding access to all of the internal features from php (currently there are too many IOCTL-s used), with that it will be possible to implement custom API with just PHP - it seems to work nicely in fastcgi mode with lighttpd.
Temporary there are two web servers running in the camera - port 80 - boa, port 81 - lighttpd (seems to be some 20% faster). You may try
http://192.168.0.7/phpinfo.php (boa, php in cgi mode) and http://192.168.0.7:81/phpinfo.php (lighttpd, php in fastcgi mode)
--Andrey.filippov 02:30, 31 May 2007 (CDT)
