in reply to New PM Feature Request - Node Watch

Ok. For the record I would love to do this. The trouble is that I have yet to come up with or hear a plausable design. Scale is a real issue with something like this. We have several thousand active participants here and we have about a half million posts. That combines to make for potentially serious work supporting this feature.

I can think of half-assed implementations that wouldnt be too much trouble, and probably would scratch most of the itch. It wouldnt be too difficult to allow users to store root nodes of threads and then use the RAT to display them on user request, but the minutae of handling things more specifically than that escapes me.

If someone can offer a reasonably sane design that seems like it would work id give it a go, but currently I dont think there is much that I can do. BTW, before anybody replies with a design please familiarize yourself with the design of the everything engine.

---
$world=~s/war/peace/g

  • Comment on Re: New PM Feature Request - Node Watch

Replies are listed 'Best First'.
Re^2: New PM Feature Request - Node Watch
by NateTut (Deacon) on Jun 19, 2005 at 13:05 UTC
    demerphq thanks for looking at this for me. I think the RAT would be very useful.

    I'm fairly new to PM but I have a background in databases so naturally a db solution springs to mind (my mind at least). Do you have any links to documentation on the "everything engine" I'm not familiar with it.

      Regarding links to everything engine, take a look at the bottom of any page on the site. Regarding a DB solution, yes sure it would have to be in DB. But the question is how. More explicitly but briefly the problem is how do you efficiently handle thread watching when you are using a parent pointer representation for the reply tree.

      ---
      $world=~s/war/peace/g

        Do you mean that nodes store a pointer to their parent, rather than storing pointers to their children?