You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several fields in the Message type that are used by Colony internals, that if modified by a user, could create mayhem.
For instance, if a service could receive messages and change MessageID, Time, ContentType, Topic, etc, and "respond" and who knows where the message would go or what it would do. IMO, any field expressing state within Colony should be hidden or have some kind of getter.
The text was updated successfully, but these errors were encountered:
I think getters is a good idea.
On Jul 28, 2014 5:40 PM, "nik hanselmann" [email protected] wrote:
There are several fields in the Message type that are internally used by
Colony internals, that if modified by a user, could create mayhem.
For instance, if a service could receive messages and change MessageID,
Time, ContentType, Topic, etc, and "respond" and who knows where the
message would go or what it would do. IMO, any field expressing state
within Colony should be hidden or have some kind of getter.
—
Reply to this email directly or view it on GitHub #8.
There are several fields in the
Message
type that are used by Colony internals, that if modified by a user, could create mayhem.For instance, if a service could receive messages and change
MessageID
,Time
,ContentType
,Topic
, etc, and "respond" and who knows where the message would go or what it would do. IMO, any field expressing state within Colony should be hidden or have some kind of getter.The text was updated successfully, but these errors were encountered: