Those are actually pretty rare in my experience, but "agent" itself seems like it would work.
-
-
Replying to @marcan42
To me, "agent" implies the exact opposite power dynamic - an agent of X has the authority to act as a substitute for X, but generally has a fair bit of discretion in doing so.
1 reply 0 retweets 1 like -
Replying to @azonenberg @marcan42
As opposed to a scenario where Y must do as X commands and has no choice in the matter, which is something that would normally be termed a "slave".
1 reply 0 retweets 0 likes -
Replying to @azonenberg
The thing is "power dynamics" are rarely much of a thing in technology, given that usually there is no free will involved. Things usually do what they're programmed to do, so there is no "choice" distinction, right?
1 reply 0 retweets 1 like -
Replying to @marcan42
They do what they're programmed to do, yes. But in a distributed system some entities have a control relationship over others. Some parts execute any command they're given while others think about it, reject some according to policy, etc.
1 reply 0 retweets 1 like -
Replying to @azonenberg @marcan42
What i'm really getting at is, don't blindly replace one word with another unless you understand all of the subtle implications that has to the engineers reading the documentation. There likely isn't a 1:1 replacement for any problematic term.
1 reply 0 retweets 1 like -
Replying to @azonenberg
Well, as I expressed in a previous thread we're already abusing master/slave in contexts where it has nothing to do with control, so the meaning is already all but totally diluted :-) E.g. for I²C "initiator/responder" makes a heck of a lot more sense.
1 reply 1 retweet 0 likes -
Replying to @marcan42
Exactly - but if you're picking new terms, pick ones that make sense *in the context of the system you're using them in*.
1 reply 0 retweets 0 likes -
Replying to @azonenberg
Yup. Do you have an example of a case with more of a control relationship? I guess something like JTAG would qualify, but for that one we're already using "debug target".
2 replies 0 retweets 1 like -
Replying to @marcan42 @azonenberg
SPI slaving of a microcontroller, where the main UC controls the slave UC?
2 replies 0 retweets 0 likes
SPI is a comms protocol, it doesn't imply control. "host/device" sounds a lot more appropriate for that use case.
-
-
Or even "client/server".
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
So that means we then have HODI and DOHI pins?
1 reply 0 retweets 0 likes -
Actually, I was thinking of USD/DSD (upstream/downstream data). Shorter too.
0 replies 0 retweets 0 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.