Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Devstatus

...

Statusimplemented

...

Target

...

forum 2.0

 

* Provide means to synchronize Magnolia-based forums with other means of communication, such as mailing-lists. See MGNLFORUM-130@jira.

Status
Primary target: our own forum with our own nntp-archived mailing lists.

Observation (exporter) and scheduled task (importer)

...

I've had some reasonable success at using Kerio's NNTP with commons-net: http://commons.apache.org/net/Image Removed
Still looking for alternatives as commons-net's api isn't superb, and has some scary longstanding issues: https://issues.apache.org/jira/browse/NET-298Image Removedhttps://issues.apache.org/jira/browse/NET-276Image Removed

-> will use email instead, as Kerio's NNTP implementation does not support the NEWNEWS command.

...

  • Implement an observer/listener pattern on forum instead of relying on jcr ?
    • would match the idea of having ForumManager return Forum, Thread and Message bean instances instead of exposing jcr nodes.
    • jcr observation can filter per node type but it filters on the parent node type, ie we need to filter for mgnl:thread and mgnl:message (the latter, because messages can be nested), and thus we can't use ForumManager.getMessage() directly from the EventListener. The EventListener would have to 1) fetch the node and check its type 2) either bypass ForumManager altogether or let ForumManager re-fetch the node
    • we still need deferred and buffered execution of events if possible, so I need to look into reusing info.magnolia.cms.util.DelayedExecutor or the java.util.concurrent package.
      This has not been implemented yet, but is still an open option for the future.