|Anonymous | Login | Signup for a new account||2019-07-22 20:45 UTC|
|Main | My View | View Issues | Roadmap | Repositories|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000567||Tunix||FreeEMS Plugin||public||2012-04-06 22:32||2012-04-07 12:36|
|Target Version||0.9.24||Fixed in Version|
|Summary||0000567: Re-Add Datalog Polling Service But In A Clean Independent Way|
|Description||MTX used to poll for logs, and not be able to handle streamed logs. It should be capable of doing either.|
Polled logs have their place, as does streaming mode.
Dave ripped out the polling service when restructuring the serial service to work correctly. When asked to put them back in, he said he couldn't because they have the same packet ID. This is invalid reasoning.
The way it SHOULD work is that a handler service is subscribed to the log packet id and doesn't care where they come from. This decouples the requesting and the handling from each other allowing a the polling service to seed the requests and the handler to handle them equally whether they were requested or streamed.
|Tags||No tags attached.|
No they cannot work easily. It is one or the other. You're breaking the API in an odd way by saying "this is both an apple and an orange"....
streamed logs should have one ID, requested logs should have another, as they are two different contexts (I. I asked for this one, but the other one jsut gets shoved down my throat). It also allows the future capability of defining the requested log to be a subset of the main log, and then it MUST have it's own ID to be able to be parsed appropriately.
|Copyright © 2000 - 2011 MantisBT Group|