Christopher Warner

Email below sent at work but useful to see how Krang using ActiveMQ is progressing. So far so good there are some sql calls and stuff that need to be broken down when Krang goes to put all this stuff together and once we replace the category chooser with what Andrew has been cooking up it’s gonna be so much faster. I’m thinking we should Ajaxify all of the widgets; I remember reading on the devel-list this would be in Krang 3.0 or something? I’m not sure but it’s safe to say we are beginning to divert; instead of rewriting ajax widgets outright Andrew is using YUI which Yahoo has released via the BSD license (thanks yahoo). The only major thing i’m worried about is listings; once that’s figured out sufficiently enough I think we’ll be safe in fully forking and doing whatever we want.

Pound on it; you guys have been giving it light beatings. That aside a
couple of things are going to change here later in the afternoon so if
you try then and it’s broken I’m aware.

1. I’m going to use xml for all of my messaging. Right now, i’m just
sending the story_id. This is fine for now but it’s feeble and plus i’d
be able to segment story/media/listings. This extends things a bit so if
you want just media alone or listings alone you can do that. I’m a
little worried about listings and it’s functionality but it can’t get
any worst.

2. Thread pool; I’m gonna do this work and everything will probably
break. Krang wasn’t really written with thread safety in mind and
bolting it on afterwards probably isn’t the greatest idea in the world
but we’ll see what happens. If all is well publishing would end up being
even faster with lustre taking a tremendous beating.

3. http://dev11.dev.nymag.biz:8161/admin/queues.jsp
You can see what’s in the queue, what’s pending, delete an entire queue
or delete a specific message in the queue. It provides atom/rss feeds
which seem to be broken in this snapshot. However when it works
basically we’d be able to put up an ajax applet some where and we can
sit and watch how cool it looks to see people publish in real time.

4. ActiveMQ 4.1.1 caused issues in regards to the webconsole broker
which I needed to start for above. Had to upgrade that to a 4.2
SNAPSHOT.

5. Sub class Net::Stomp into Krang, make it optional (maybe); if we
can’t connect to ActiveMQ add routines to fall back to slow original
Krang publish mode.

6. Jabber messaging confirmation; this is coming soon, the way I
originally did this isn’t going to work. The problem is this; because
every story has a bazillion other stories, media, listings associated
every time a publish is complete a message was sent. That was obviously
retarded. Must think of a better way.

If anyone has any suggestions for 6 or any cool ideas I can steal and
use as my own; please let me know i’m going to try and get all my other
stuff done so I can play with some of this stuff this afternoon.

There is a bug I need to report where if you have the mail-notifier-plugin loaded via Evolution and you are trying to connect to an Exchange server and your password has expired. The mail notification plugin will cause Evolution to hang. What you need to do is remove mail notification from your notify panel and restart Evolution.