Added memory scaling to StatusRLV

Experience with the old OnlineService prior to it hitting the 64kb
limit shows that it is in fact safe to use dynamic memory even on data
heavy scripts like this one which have large spikes by using an aggresive
allocation when necessary.
Added memory scaling to ServiceRecever.lsl

Experience with the old OnlineService prior to it hitting the 64kb
limit shows that it is in fact safe to use dynamic memory even on data
heavy scripts like this one which have large spikes by using an aggresive
allocation when necessary.
Move dataserver event from requester to receiver where it should be