Workload Scripts(llCreateLink

Hey yal, I am working in a project that i need to "rebuild" multiprim objects quickly using LLCreateLink. These objects are prolly ranging from about 5 to 100 prims, so with the delay built in it could take over a minute to link the object. I was wondering if i could get some input on using small modular scripts to essentially multithread the linking process using linked msgs? Since the link order is being used by other scripts in the object i need to make sure that stays the same. Is this possible if i am sending multiple linked messages to separate scripts that are doing the actually linking?

Thanks
O

How about using part of the prim's name or description to assign its role, rather than the hard-to-maintain link order?

Thanks Argent,hadn't thought about trying that. Was more concerned with making sure the original object remained completely intacted... Ok since im trashing the link order issue.... here is another question.... would it be more efficient to send out individual link requests to each script individually or send a list of them(thinking about using strided lists) and have each script parse out the key to link based on the id# i assign it?

I just had a conversation with Strife Onizuka about this, and as a result I've abandoned a similarly complex but generic mechanism and gone much simpler, using bitmaps in the number field to filter messages to groups of links.

It would depend on how many links you had, and how many discrete sets you needed to communicate to... but, for example, if you have 100 links but most of them behave the same so there's only 30 discrete behaviouors, you could send out a link message with a "1" but for every group of links that need to act on it. Then you could send out a message to all links which would do something like this:

state_entry()
{
  my_id = some_function_of_description();
  my_id_bit = 1 << my_id;
}
link_message(integer from, integer num, string str, key id)
{
  if((num & my_id_bit) == 0) return;
  do_something_with(str, id);
}