in reply to Universal request objects

You're not looking for Catalyst::Request - you're looking for Catalyst::Engine. In the C::R docs, it says that it's filled in by C::E. So, you need C::E subclasses that DWIM, plus some dispatcher that uses the right C::E subclass.

Sounds to me like you just want to use Catalyst and go from there.


My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Replies are listed 'Best First'.
Re^2: Universal request objects
by Ovid (Cardinal) on Dec 23, 2005 at 19:19 UTC

    Actually, we don't want to use Catalyst. There is a Catalyst component, but it's optional. Thus, if the users don't want to install it, they shouldn't be dependent on it.

    Cheers,
    Ovid

    New address of my CGI Course.

      Break out the parts you want, create a new CPAN module, and offer it back to the Catalyst devteam as a separate distro that's useful without the rest of Catalyst. Then, Catalyst can use it as a dependency.

      My criteria for good software:
      1. Does it work?
      2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
      The Catalyst::Engine standalone rewrite is called Isotope, and although it's being worked on, the author is apparently somewhat famous for not commiting very often.

      Some time early in the new year, I'm going be (hopefully) helping to get Isotope $done, so I can replace the engine-layer of my own web application system with it.

      With you and I and a few others, I reckon we should be able to push it through to completion reasonably promptly. What do you say? :)

        Which sounds really nifty, but I have to get this done now. I already have a basic implementation (pretty specific for our needs). I like the thought of Isotope, but I need to get my core needs done and move on :/

        Cheers,
        Ovid

        New address of my CGI Course.