>>>>> "NT" == Nathan Torkington <[EMAIL PROTECTED]> writes:
NT> Can anyone make head or tail of the language? Does it pretend to NT> cover (or is it invalidated by) 'use Module VERSION'? It looks like NT> it might even apply to some kind of web templating systems, but I NT> can't understand enough of the "claims" to figure out what the hell NT> it's talking about. ok, here is my take on a quick skim of it. the core claim is basically a high level buffer passing API for a library of modules. he uses perl's require just to illustrate the loading aspects. first there is some module location stuff (he keeps mentioning finding it by some name matching) but other criteria could be used (phase of moon? :). then the module is loaded and run. somehow a call to some get_buffer routine is made and that is filled with data and sent to the module which crunches it. it then sends back data (HTML is his example) via another buffer. sounds like a bad version of message passing to me. :) so i bet this was just a patent on how this guy at cisco did did some dynamic module loading and calling (in perl i bet). i doubt it would be enforceable since that sort of concept is not new. wrapping all modules in a common api and loading and calling based on criteria isn't new stuff. i wouldn't worry about it. it would be so hard to defend and there is plenty of prior art IMO. apache modules behave similarly i think. i am sure there are other older systems that can polymophically load and execute modules. uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com ----- Stem and Perl Development, Systems Architecture, Design and Coding ---- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org Damian Conway Perl Classes - January 2003 -- http://www.stemsystems.com/class
