link message contention?

Short question: What happens when script "A" broadcasts "send me info" via link message and scripts B, C, & D send info at the same time?

Long question: I (will) have a parent script that can have 0, 1, or more child scripts to feed it data via link message. I'll contextualize this to make it concrete: I have a cushion which uses Strife's wonderful script fragment to change the sit target without an unsit; this allows a chair (or whatever) to have multiple poses.

I want to provide pose sets (such as formal, casual, romantic, bdsm, etc) that can be loaded into the cushion. Since the cushion is actually part of a larger piece of furniture which can rez "n" number of cushions on demand, I can't store the animation information in a notecard due to performance reasons - I can't expect someone to wait 10 seconds to load a set of poses. Another consideration here is that the child scripts will be sending multiple lm's to populate the parent script.

Can I safely count on lm's to be queued up like, 100% of the time, or do I need to add in some traffic management code as well -- ie
A: "SERVICE DISCOVERY"
B: "SERVICE CASUAL"
A: "ACK CASUAL"
A: "XMIT CASUAL"
C: "SERVICE ROMANTIC" (lm out of order because of lag)
B: ...data 1...
B: ...data 2...
C: "SERVICE ROMANTIC" (repeats until acknowledge)
A: "ACK ROMANTIC"
B: "DONE CASUAL"
A: "ACK CASUAL"
A: "XMIT ROMANTIC"
...etc.

short answer, you can have upto 64 events saved up in the stack, anything after that is lost

Don't count on the messages coming in in the order sent. One message may be delayed a bit more than another changing the order of them.

Use a sequence numbering system to keep track of the ones from each of the children the sequence can then be assured and missing ones detected, but it will not cover the case between different children sending messages. Thats a whole new ball game.

Not so much. The linkmessage event includes the linknum of the sending prim. It's just a matter of using that linknum.