This does come down to a bandwidth issue as that ‘freedata’ is used for sending what I’ve been told, metadata and that sort of information about objects. However, from my own knowledge of further down, 3000 is too big. It will fail at about 1300 or so due to the normal packet MTU of 1500B.

That data wont be split up and multipacketed either, so if there’s a need to have large metadata fields about objects, perhaps the way to go is to either implement a multipacket version, or move the request over to HTTP.

ScheduleRexPrimFreeDataUpdate(true);
}
}

This is implemented similarly in modrex.

That being said, if this is something that is transmitted to the viewer – factor bandwidth into your calculations (obviously if you reaaaally want to you should be able to, but it’s worth keeping in mind)

thanks for all the work on modrex!
Coincidentally, I published a piece a few days earlier on using the rexdata panel with the Python CompObj library to supply configuration parameters in inifile format.

While browsing the code I noticed that there’s a hard-coded limit of 3000 characters on the rexdata blob in the original code and in modrex. It seems a bit arbitrary and low. The maximum blob sizes in the supported databases are:
SQLite: 2**31-1
MySQL: practical limit is 100’s of MBs due to triple copies being maintained
MSSQL: 2GB

I’d like to see the size lifted to a larger value, perhaps configurable in OpenSim.ini. What are your thoughts on this?

– Peter