tag:blogger.com,1999:blog-8677320456287245517.post275951731233044568..comments2023-10-01T03:24:41.639-10:00Comments on HackyHawaii For Life by AK: hackystat problemsaaronhttp://www.blogger.com/profile/14904770558911719358noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8677320456287245517.post-13339302855665754442008-02-10T19:45:00.000-10:002008-02-10T19:45:00.000-10:00> A regular user shouldn't need to worry about the...> A regular user shouldn't need to worry about the DailyProjectData service or even know its there.<BR/><BR/>I agree. But, a developer should be able to see the data coming in and the data coming out. Thats the only way to debug a service that isn't yours.aaronhttps://www.blogger.com/profile/14904770558911719358noreply@blogger.comtag:blogger.com,1999:blog-8677320456287245517.post-22799679092268883202008-02-10T07:31:00.000-10:002008-02-10T07:31:00.000-10:00Hi Aaron,No, it's not you. There is a problem wi...Hi Aaron,<BR/><BR/>No, it's not you. There is a problem with the DPD service which makes the TelemetryViewer take too long to respond to requests. <BR/><BR/>A regular user shouldn't need to worry about the DailyProjectData service or even know its there. <BR/><BR/>Your interpretation of the sensordatabrowser vs. viewer is correct. <BR/><BR/>It might be a good idea for the sensordata viewer to fetch the last hours (or whatever) of data on startup so that the order in which you bring things up doesn't matter so much. But I generally recommend that people just use the sensordata browser. <BR/><BR/>Cheers,<BR/>PhilipPhilip Johnsonhttps://www.blogger.com/profile/12095636274313170271noreply@blogger.com