Probably, but I'd do it as:
my $in = $IN->get_hash;
and then pass %$in as there tends to be some random issues with passing complex data structure strings. These big long complex statements look cool, but there is often less trouble with a few shorter ones.
Actually, as I said, %$IN isn't really needed, it was an afterthought. There *are* problems with passing $IN in any form -- ie: only data that has been somehow "approved" should be passed on.
That's probably why I didn't do it before... but I wasn't having users login either. $USER is needed to pass the login information on through. That was the main idea here.
With the power of the template parser, your programs that call it should really know what is being passed in to them, and what is being sent out. If you need to accept arbitrary variables, prefix them prefix_ and pick them out, and check them out before sending them on. It's easy to get lazy, and to get caught up in the power of passing hashes, but good protection never goes out of style :)
All these plugins are undergoing rework, and updating to a more "modern" logic for Links 2.1.2 and above.
Once Community is released, my progamming will probably be limited to scripts that work under that, as all my site networks will be sharing different community "shell" log ons. We have 3 main projects going on, so it looks like 3 "communities" will be enabled.
I'm just really out of *time* to do anything. I'm working on a stress-related, sleep-deprived heart attack as it is.
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
my $in = $IN->get_hash;
and then pass %$in as there tends to be some random issues with passing complex data structure strings. These big long complex statements look cool, but there is often less trouble with a few shorter ones.
Actually, as I said, %$IN isn't really needed, it was an afterthought. There *are* problems with passing $IN in any form -- ie: only data that has been somehow "approved" should be passed on.
That's probably why I didn't do it before... but I wasn't having users login either. $USER is needed to pass the login information on through. That was the main idea here.
With the power of the template parser, your programs that call it should really know what is being passed in to them, and what is being sent out. If you need to accept arbitrary variables, prefix them prefix_ and pick them out, and check them out before sending them on. It's easy to get lazy, and to get caught up in the power of passing hashes, but good protection never goes out of style :)
All these plugins are undergoing rework, and updating to a more "modern" logic for Links 2.1.2 and above.
Once Community is released, my progamming will probably be limited to scripts that work under that, as all my site networks will be sharing different community "shell" log ons. We have 3 main projects going on, so it looks like 3 "communities" will be enabled.
I'm just really out of *time* to do anything. I'm working on a stress-related, sleep-deprived heart attack as it is.
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
