search

waltz-controls / rfc

RFCs for Waltz-Controls
MIT License
2 stars 3 forks source link

Define a way to transmit magix intrinsic errors #18

Open altavir opened 3 years ago

altavir commented 3 years ago

An example: the message got sent to a client that could not accept it. I think we need a separate kind of system payload with format equals magix for such messages. We can use it for watchdogs and other services.

Ingvord commented 3 years ago

An example: the message got sent to a client that could not accept it.

What does it mean in this case? Message can not be delivered while e.g. the upstream endpoint is down? We won't know about that, because currently the idea as that Magix has no clue about its clients, it just broadcasts whatever message is passed to the broadcast. Underlying transport may however detect that some of the endpoints are down e.g. there is such mechanism in SSE and probably in others not guaranteed though. So in theory we could send back a report with undelivered messages like in email...

Speaking about watchdogs for me its more application specific feature, we should be careful about it, but of course further discussions are welcome

altavir commented 3 years ago

OK. Let's put it on hold. The current architecture allows to add any number of auxiliary message formats.