Closed zippy closed 8 years ago
this joins together #44 & #43
as of 8ba566a61b89d5d6 REQUESTs store END_CONDITION in the PENDING_RESPONSES so we can manage our own cleanup of pending requests. Also the END_CONDITION is now part of the ENVELOPE of requests. Still to do, to pass that information through into the listener on the the other end.
as of bae6d609d0 expectations now store END_CONDITIONS and its an optional parameter to LISTEN, but checking the value(s) for removing the expectation still needs doing.
checking the END_CONDITIONS TIMEOUT_AT value brings up our long known intention of adding processes to structures and symbols, because we need to compare the timeout values to eachother to do the timeout. I've added #75 to finally get this on our list. However for this particular case I'll probably do a hard-coded c implementation of comparing TIMESTAMP values for speed, because we do it so often, but this is something that could easily be implemented in ceptr itself.
as of a7c5db3785 TIMEOUT_AT being checked for both REQUEST and LISTEN
this should allow variability in how long the process lives: time/count
requires new symbols REQUEST_CONDITIONS, REQUEST_TIMING,REPETITIONS