Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Is llSay unreliable?
blaze Spinnaker
1/2 Serious
Join date: 12 Aug 2004
Posts: 5,898
11-25-2004 03:26
For massive object to object communications, would you say llSay is unreliable when link messages are not an option?
_____________________
Taken from The last paragraph on pg. 16 of Cory Ondrejka's paper "Changing Realities: User Creation, Communication, and Innovation in Digital Worlds :

"User-created content takes the idea of leveraging player opinions a step further by allowing them to effectively prototype new ideas and features. Developers can then measure which new concepts most improve the products and incorporate them into the game in future patches."
Till Stirling
Crazy Inventor
Join date: 31 Jul 2004
Posts: 124
11-25-2004 05:35
Unless the distance between the objects is within hearing range and you are using a channel (>500), that does not have to much spam from other applications it should work ok.

I have built several c/s-appliactions, that communicate with llSay/llShout and have so far not encountered any problems. My latest project, a scanner-system which can cover several sims, is transferring large amounts of data this way in both directions.

Till Stirling
_____________________
Our Shops:
SilverDay Castle in Degar (228, 108)
SilverDay Shop in Atlas (75, 156)
Cosy Market on Cosy Home (28, 137)

SL Boutique: http://www.slboutique.com/Till_Stirling/
SLExchange: http://www.slexchange.com/modules.php?name=Marketplace&MerchantID=113
Christopher Omega
Oxymoron
Join date: 28 Mar 2003
Posts: 1,828
11-25-2004 10:04
From: blaze Spinnaker
For massive object to object communications, would you say llSay is unreliable when link messages are not an option?

I pretty much agree with Till, but it also depends upon what you mean by "massive object to object communications". Are we talking several hundred messages per second? Or just a large number of messages on average within a certain long period of time?

Object chat functions are quite unreliable when it comes to the former scenerio. The event queue can only expand so far; since LSL is slow compared to other languages, even a short listen event can cause the event queue to bloat when too many messages are heard.

==Chris
blaze Spinnaker
1/2 Serious
Join date: 12 Aug 2004
Posts: 5,898
11-26-2004 01:42
Well, I have definitely encountered problems with lots of messages. I was able to pretty much reproduce it with 500 messages and 5 listeners.

However, I'm really not that massive. I think maybe 10-20 messages per second?

I have to do shouts because rezobject rezzes in the geo center rather than root position (gRRRR), and my objects can be arbitrarily large.
_____________________
Taken from The last paragraph on pg. 16 of Cory Ondrejka's paper "Changing Realities: User Creation, Communication, and Innovation in Digital Worlds :

"User-created content takes the idea of leveraging player opinions a step further by allowing them to effectively prototype new ideas and features. Developers can then measure which new concepts most improve the products and incorporate them into the game in future patches."
Pete Fats
Geek
Join date: 18 Apr 2003
Posts: 648
11-26-2004 01:58
From: blaze Spinnaker
I have to do shouts because rezobject rezzes in the geo center rather than root position (gRRRR), and my objects can be arbitrarily large.


They have added llRezAtRoot() in 1.5.7 (I think that was the version) Try it out, it might be helpful.
_____________________
Till Stirling
Crazy Inventor
Join date: 31 Jul 2004
Posts: 124
11-26-2004 03:49
From: blaze Spinnaker
Well, I have definitely encountered problems with lots of messages. I was able to pretty much reproduce it with 500 messages and 5 listeners.
QUOTE]

For that reason I did several things in my sensor-net:

1. The server uses ONE listener only!
2. The server queries one sensor after the other
3. All sensor-messages are put into an internal queue which is processed after the last sensor finishes its report.

The important part with massive-msg-transfer through the say-api is to keep processing of the messages during the actual-transfer to an absolut minimum. I have one if-clause for protocol-commands, and one if-clause in the datagathering statement. All other processing (dataserver-requests, list comparisons, etc.) is done by calling a processing state, which after completion returns control to the main loop.

Another possibility is to pass the messages via linkmessage to another script which then does the processing of the message. which works equally well for certain applications.

Till Stirling
_____________________
Our Shops:
SilverDay Castle in Degar (228, 108)
SilverDay Shop in Atlas (75, 156)
Cosy Market on Cosy Home (28, 137)

SL Boutique: http://www.slboutique.com/Till_Stirling/
SLExchange: http://www.slexchange.com/modules.php?name=Marketplace&MerchantID=113