From: Sam Moore Date: Fri, 6 Sep 2013 17:00:08 +0000 (+0800) Subject: Automatic commit of irc logs X-Git-Url: https://git.ucc.asn.au/?a=commitdiff_plain;h=202b21b110e9165a90e49e03b87978e812266eaa;p=matches%2FMCTX3420.git Automatic commit of irc logs --- diff --git a/irc/log b/irc/log index eb4e3be..84d928d 100644 --- a/irc/log +++ b/irc/log @@ -1948,3 +1948,25 @@ 18:51 < jtanx> hm, so to get clock_gettime to work, you need to use std=gnu99 instead of std=c99 18:52 < jtanx> do you think we should just stick with gettimeofday? 21:46 -!- jtanx [~asfa@203-59-42-232.dyn.iinet.net.au] has quit [":3"] +--- Day changed Fri Sep 06 2013 +09:16 -!- jtanx [~asfa@130.95.133.183] has joined #mctxuwa_softdev +12:05 -!- jtanx [~asfa@130.95.133.183] has quit ["ChatZilla 0.9.90.1 [Firefox 23.0.1/20130814063812]"] +13:03 -!- jtanx [~asfa@203-59-42-232.dyn.iinet.net.au] has joined #mctxuwa_softdev +16:05 < jtanx> I was just thinking, what sort of identification information is needed from the server? +16:05 < jtanx> The gui should have some understanding of what sort of sensors/actuators it needs to display +16:10 < jtanx> it might be enough to say this is API version x +16:10 < jtanx> and at version x, it's agreed that these id values correspond to these sensors/actuators etc? +16:19 < jtanx> anyway, what I've done for now is if asked, the api will list the sensor/actuator ids and the corresponding human readable string +16:19 < jtanx> api/?sensors&actuators +18:06 < jtanx> also, what do you think of keeping track of the number of points stored +18:07 < jtanx> then you can allow the user to request from where they want to retrieve data from and how many to retrieve +18:08 < jtanx> the only problem is that it wouldn't be time based, but based on the number of data points recorded +18:08 < jtanx> this method is simpler because you now the offset to use with fseek +18:08 < jtanx> if it's time based you have to search the data for the correct point +19:51 < sam_moore> All the above makes good sense +19:52 < sam_moore> If we can make a working "request X number of points" first instead of "request from time T onwards", we might be able to convert the latter to the former if necessary +20:04 < jtanx> ok I just submitted a pull request for some stuff +20:04 < jtanx> mostly the identification stuff and some reordering +20:04 < jtanx> FCGI_RejectJSON now requires that you give a description explaining why +20:05 < jtanx> when RejectJSOn is called, it's always logged along with the description, so some of the current log messages within the handler functions may be redundant +21:11 -!- jtanx [~asfa@203-59-42-232.dyn.iinet.net.au] has quit ["ChatZilla 0.9.90.1 [Firefox 23.0.1/20130814063812]"]