Thread: Maximun RR variable data size

The variables are VB6 strings, so in theory the limit is 2Gb, but real limits will definitely depend on memory and many other factors. The bigger the strings the slower they may be to handle and remember that some characters have special meaning in RR so if you use some special characters you may not be able to use certain functions with the variable.

Guino,

Thanks.

I'm thinking of storing a JSON or XML string to share between a plugin and a couple of apps I am writing so as to cut-down on internet traffic.

Using RR variables will save me the trouble of using Windows shared memory.

I shouldn't have character set issues but will scan the strings anyway.

Could you comment on the characters tht might be trouble?

That raises another question, does RR look at the content of the data when processing either a SETVAR or GetInfo?

Regards,
Jim

If you use the plugin specific commands to get/set user variables, you don't have to worry about special characters - it's only when trying to use the variables in commands (i.e. "COMMAND;$VAR$") that you should worry about things like ||, <<, >>, ++, etc.

That raises another question, does RR look at the content of the data when processing either a SETVAR or GetInfo?

of course it does...

look at this..

"SETVAR;myvar;blabl||test"

in a plugin, you should NOT be using SETVAR, use .SetUserVar()

mitch,

I just found GetUserVar and SetUseVar.

I've just gotten back to an old plugin that contains an SDK that doesn't have those and out of habit I had continued to use SETVAR.

I have since switched all of my plugins to use the most recent SDK (10/1 - haven't downloaded 11/1 yet).

BTW, I knew the answer to the SETVAR question and don't know why I asked.

Guino answered the the same question about SetUserVar that the content isn't scanned.

Regards,
Jim

no problem...but FYI
the SDK hasnt changed(additions) in quite some time...
since 11/2010!!
yes 2010!!!
SetUserVar/GetUserVar been there since 11/2010
read history.txt

He did state that it was an OLD plugin that he started...

I'm not sure history.txt is the ideal place to look for changes to the SDK (even if they do rarely occur) SDK documentation should exist in a separate entity, preferably with each addition being added to the extension plugin examples. The idea is to make it easier to open up VBS and code right?

they are in the examples... do i hear you volenteering for documentation help?