Update the plugin interface to use a parameter collection

[matthewste]

Currently plugins get passed Param1 and Param2, to allow for plugins to be sent more parameters the interface should be updated to pass a collection which would allow for an unrestricted number of parameters

[bwoodworth]

This would be a great thing to add to v0.4.4. It is pretty complex so maybe we should have a discussion about the best way to go about it.

[KHerron]

Could it be something as easy as adding a common separator?
For example "::" or "++" like this - object.Run Method.Method(param1::Parm2::param3::param4)
Then it would be up to each plugin to count how many parameters were passed and how to use them.

If so, then we could leave the core as it is, and just update the plugins and still have Param1 and Param2 giving us really unlimited parameter combinations.

Just two cents from my piggy bank.

[VaughnRupp]

It currently does take multiple parameters. It is confusing, but like the script processor, takes PARAM2, and spilts the values by ,
So we do have comma separated multi-parameters now. Perhaps a collection or some other construct would be neated and safer as the current , is not very safe.

[VaughnRupp]

Reference the current Jabber plugin and it is using 3 parameters, not 2. =)
������Jabber.Run Method.Send From List.Vaughn,Speech List,Time

It is using Vaughn in PARMA1 and Speech List,Time in PARAM2, which Jabber parses PARAM2 for as many parameters as it wants.