Unintentional Random...

Plugins & Plugin Development General Plugin Discussion
1

I wrote three simple plugins this week and they are all exhibiting a strange phenomena. It’s probably one error that I’ve propagated with my cut-and-paste development technique. What happens is that every button-driven action apparently includes a request for a random number. See log:

08 04/13/13 14:15:50.922 JobHandler_LuaUPnP::HandleActionRequest device: 96 service: urn:dcineco-com:serviceId:MiLightRGB1 action: ctrl_chr[36;1mOffctrl_chr[0m <0x323a7680> 08 04/13/13 14:15:50.922 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=96 <0x323a7680> 08 04/13/13 14:15:50.923 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:dcineco-com:serviceId:MiLightRGB1 <0x323a7680> 08 04/13/13 14:15:50.923 JobHandler_LuaUPnP::HandleActionRequest argument action=Off <0x323a7680> 08 04/13/13 14:15:50.923 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.33794783311896026 <0x323a7680>
Now there is nowhere in my implementaton code where I’m calling for a random number. The request appears on actions both with and without arguments and I can’t see anywhere that I’ve left an orphaned tag or table entry. With the exception of the strange log entry, all the actions are working fine.

Any suggestions as to where I should look for the cause?

2

I know that in the HTTP world, random numbers are often used to spoil any caching that might be in the pipeline, so MCV might be adding the random numbers for a similar purpose. I’ve seen it elsewhere in my Vera logs but I don’t know the background in this context.

watou

3

It’s added by the default UI, probably because they don’t add the correct HTTP response headers that indicate not to cache the content (Cache-control etc).

It was added a looooooong time ago.

4

Thanks @watou and @guessed.

I believe I have learned: It isn’t something I did wrong; It isn’t doing any harm; There’s nothing I can do to stop it anyway. ;D