>>>>> "Randal" == Randal L Schwartz <[EMAIL PROTECTED]> writes:
Randal> Has anyone moved the class methods and class vars to the instance side Randal> so that multiple PWS instances can co-exist? Randal> I remember this being an issue a few years ago. Now I had a practical Randal> reason. Randal> If no one has it, I'll hack out a CS myself and submit it. A few more design thoughts on this, since no-one has responded yet: All the class methods would become instances methods. A single DNU handler would be added to the class to delegate all former class methods to a singleton, lazily initialized as "PWS new". That way, the new PWS would be upward compatible, and yet permit distinct concurrent web servers in the same process by creating multiple instances. All the current class vars will become instance vars. Does using a DNU handler make sense here? Or should I just redirect only the explicit existing methods? If the DNU redirect fails, the error will be against a newly-made PWS instance, which probably makes sense from a debugging perspective. :) I'd like to also be able to subclass PWS, so I'll be looking carefully at refactoring any other classes mentioned, and make them method calls against self instead, so they can be overriden. Who "owns" PWS right now? Am I stepping on someone's toes? -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[EMAIL PROTECTED]> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
