Kano, sorry haven't checked this thread recently, with Thanksgiving last week. Didn't realize someone was going to take this on so quickly (and cheaply
j/k)
Anyways.. see my comments inline below.. please forgive the newbishness of some of my questions..
The .php would be run locally?
6 files added/changed from current ckolivas master:
main.c, miner.h, AUTHORS, api.c, api-example.php, Makefile.am
(also has the updated linux-usb-cgminer)
OK so this obviously isn't final (though it does work fine for me)
Anyone who can build their own cgminer and is interested could you have a look?
Not sure if this should have been mentioned earlier, but I need a windows version and unfortuantely I can't build from scratch.
It currently has 3 API commands:
apiversion - returns a version string "0.1"
dev - returns a status string of all the devices (CPU and or GPU)
pool - returns a status string of all the pools
Do the status strings differentiate the data returned as to which "rig" and which GPU on said "rig"? ie. Is the name of the "rig" returned with the status string? Or we have to remember which one were were just talking to when we got the status return?
The included PHP file (api-example.php) simply converts the returned string into a data structure
Very simple and very easy in PHP the way I've done it.
No I'm not expecting people to give me bitcoins yet ...
The 3 main questions I have are:
1) what other API commands do people want
2) what parameters should I add to cgminer: --api-port = 4028, --api-address = 127.0.0.1, --api-access = 192.168.5.* and anything else?
I'm assuming --api-port & --api-address is the port and address of the actual "rig" we are talking to? --api-access is the ip of the computer allowed to communicate with the rig?
the numbers shown are of course examples
(I haven't added any parameters yet)
3) what socket I/O do people want: by this I mean: default port and access restriction.
It currently runs on port 4028 and only listens on 127.0.0.1 - for security reasons of course.
I guess I don't get this. I understand listening port, but what other ip would the "rig" running cgminer listen to other than it's own?
Edit: it does no mutex locking access to the cpu/gpu/pool info since it would appear that is OK
(the current code doesn't appear to do that either)
ckolivas - does that sound correct to you?
No idea what this means.
Edit2: minor change - it wasn't closing the connection if an invalid command was sent
Edit3: added 'quit' and 'summary'
Do you have any screenshots of what frontend you have running for you right now?
Thanks!