search

zippy / ceptr

(a recomposable medium for distributed social computing) || (semantic self-describing protocol stacks)
http://ceptr.org
GNU General Public License v3.0
88 stars 17 forks source link

add handshake reject/accept handshake to REQUEST #45

Open zippy opened 8 years ago

zippy commented 8 years ago

This was async in SEND, but now provides the code that should be added as it's own pre-pre-blocked execution context as the response-point for the __r_send.

artbrock commented 8 years ago

I don't think it's about sync or async. It's about once or multiple plus a timeout (UNTIL timestamp for subscription or waiting period for even a single message response)

zippy commented 8 years ago

I've converted this to adding the reject/accept handshake to REQUEST which is separate from the question of where the actual response data gets passed to (i.e. the blocked tree, or a separate process) and which requires it's own separate timeout.

This also requires adding error handlers in our usual manner that can get triggered if the responder sends a rejection.