Large input data to plugins may cause problems Text Write Text Read String Manipulation etc

Large input data to plugins may cause problems Text Write Text Read String Manipulation etc



Title: Large input data to plugins may cause problems (Text Write, Text Read, String Manipulation, etc)




Q. How do you avoid the plugins from failing when using a larger size data as input?

A. Use file as input. Here is the explanation of what you are experiencing.

When you use variables (String) as input to your plugin, what is happening is that PAM passes on the data to the variable via Windows CMD feature which has the limit on number of characters to handle – that is 8,192 characters to be exact. PAM also passes on some metadata along with the actual payload data, consuming some of the 8,192 characters. Therefore, we recommend, when the data size (or, actually, it is the length of your string) may exceed 8,000 characters, that you select file as the input. For some plugins, however, we are aware that the file input option is not available. In this case, please report your problem at tech@argos-labs.com



Need help?

Technical contact to tech@argos-labs.com



May you search all documents,