remove message type from Emit, assume type from Announce

[nikhan]

I may not fully understand the use case, but if a Colony service announces a type it is producing, shouldn't Emit() always produce messages given by function Announce()? For example, if I declare my service is sending bees should I have to specify that each message of type bees

The exception here is if a service wants to produce different kinds of messages than what it emits, but I would say that affordance could be confusing.

I just used Emit() to send a message type different than what I announced and I am not sure that is desirable behavior.

[mikedewar]

Main difficulty there is that a service can emit multiple types.

Announce could define those content types that are allowable and emit could
error of the content types haven't been announced.
On Jul 28, 2014 5:36 PM, "nik hanselmann" [email protected] wrote:

I may not fully understand the use case, but if a Colony service announces
a type it is producing, shouldn't Emit() always produces messages given
by function Announce() For example, if I declare my service is sending
bees should I have to specify that each message of type bees

The exception here is if a service wants to produce different kinds of
messages than what it emits, but I would say that affordance could be
confusing.

I just used Emit() to send a message type different than what I announced
and I am not sure that is desirable behavior.

—
Reply to this email directly or view it on GitHub
#7.