[Tinyos-devel] problem of using FTSP and CTP

[Miklos Maroti]

> Packet senders shouldn't wire to ActiveMessageC.Send. It forces *all*
> senders to handle EBUSY on a virtualized interface, adding unnecessary code.
> It breaks scheduling fairness. The hack in 1.x to deal with this was a
> global sendDone event; let's not go back down that path.
>
> Or is the issue that there should be a TEP saying that if anything in your
> system uses AMSenderC.Send you MUST NOT wire to ActiveMessageC.Send?

No, I think it should be spelled out that ActiveMessageC MAY return
EBUSY even if you did not send a message.

And of course then AMQueueImplP.nc needs to be fixed to handle this
EBUSY return value and try it again (and not just give up sending a
message). Then the problem is not at CTP at all, any other client
would be suspect if used together with some other protocol that uses
ActiveMessageC directly.

Miklos