Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I'm curious, how are you planning to use Pixie? It looks generally useful enough but I wonder what sort of system would critically depend on its functionality...


    • We're using it for session type work. Because Pixie can handle arbitrary objects we can save pretty much the entire state of an application between transactions without having to worry about packing and unpacking everything from some tiny session object. The complicity features came about because we've got some objects and applications within the framework that hold onto DBI handles and the like, which can't be directly stored.

      Pixie's lack of schemas means we can keep some flexibility in our object model
      • Interesting. What advantages does Pixie have over the typical tied MLDBM hash per session strategy? Over Apache::Session? Maybe you could add a comparison section to the Pixie docs outlining the similarities and differences between Pixie and other solutions.


        • What advantages do *any* object persistence tools have over MLDBM or Apache::Session? Pixie deals with real objects; the user doesn't have to worry about marshalling state. It does deferred fetching, allowing the user to build complex object webs without having to worry about fetching the world (until he needs to).

          Pixie works to make sure that there's only one 'live' instance of an object in play at any given time (and, with locking can be set up to ensure that this is the case across multiple processes).
          • MLDBM uses Storable to serialize Perl structures, so it handles objects just fine. However, your points about synchronized access to objects and object webs are well taken.