Greetings, fellow monks.
I am currently working on an Ajax-driven web application, which has a data access layer written in Perl. There are two distinct entities that actions are performed on, called containers and objects. I am currently rewriting urls that look like /actions/container/create or /actions/object/delete to my actions script, and passing in a type parameter to mark whether we are to perform operations on objects or containers.
I am planning on writing a dispatch table to handle all of the available actions passed to the script, but I was wondering: is there a way to write nested dispatch tables, so that I can dispatch based on the type as well? I was planning on having separate tables for containers versus objects, but can't seem to wrap my head around how I'd go about implementing this.
Thanks,
Spidy
In reply to Nested Dispatch Tables? by Spidy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |