Syncing up the ESME server clock

Watching Dora during a "pajama party:

Howdy

Getting ready for the eBig preso

Refactoring BaFO

Watching The Shield

Archer is very happy about the tasty pot roast that made it into his food bowl

Time to write some presentations

http://dogscape.com went down for the first time in a long time... 2 years I think it is.

Upgraded all the servers... restarted without incident.

Giving an #Esme demo to Stwart

Hey... who's out there?

No. It's pretty much a work in progress. :-(

Very kewl

Okay Yak Shaving (aka #Esme related activities) over... on to writing

Got #Esme over to the new box. H00T!

Most of my domains are moved to the new box...

Getting #Esme all cleaned up for Apache... stripping views from Scala code... fun fun

It's ESME day in San Francisco

Yep. Excellent turkey, great gravy and a ton of fun hanging out with the family. How was your weekend?

Back at the desk after many days away

Working on my proposal for #Javaone09 and #Communityone09

Getting everything together for the Lift Workshop

The #Esme project is upgraded to #Scala 2.7.2

Woo Hoo #Lift will be on #Scala 2.7.2 today!!

Got a section of the #Lift Workshop nearly done... Woo Hoo!

WOrking on the #Lift #Book proposal

Working through @bill 's excellent #Esme critique

Showing Dan #Esme

I'm betting the Dow is ~6,500 on Jan 20, 2009

Playing Buy a Feature with Dan and Jorge

Panic, panic, who's going to panic?

The revisions to Lift are up on GitHub... please do a pull and an mvn clean install and things should be working again

Here's a message that contains the #Esme tag

Giving a demo to Chris from #Jive

Thanks!

@dhague -- how about putting the stack trace in the meta data and putting the exception message in the body?

Giving an #Esme demo to #Jive at 3:30PST

@bill welcome to #Esme

THanks for throwing mud at the design... which you're making incorrect assumptions about. People keep track of other people as well as messages that contain tags. If the tags are mutable, how do we deal with someone who is keeping track of a tag? If the tag is added later, do we have to go through and re-apply the tag tracking rules? If a tag is removed and that's the reason the message got into someone's mailbox, do we remove the message? There are also actions that are applied based on rules (sender, time, tags, text match, etc.) What is the effect of adding a tag to those applications? What is the effect of removing a tag from those applications? So... what's the use case for adding or removing a tag other than "I forgot"? Also, please don't be insulting about the architecture. I've been studying this problem for 18+ months and this is my third micromessaging implementation and I've got some pretty solid background in the issues with various architectures.

Any mutation to the message requires backtracking to all the places the message was passed, all the rules the message was filtered through, etc. That means keeping undo/redo logs for everything and that's very expensive.

Having mutable messages (adding tags after the message is posted, changing text, etc.) makes things an order of magnitude more difficult and less performant.

Ahoy mates, It's international talk like a #Pirate day http://www.talklikeapirate.com/tlapd08.html

Primarily FF3, but also Safari and IE6/7

Woo hoo... working with #Enthiosys dan

http://thenextweb.org/TwitterKeys/keys.php?noui=1&jump=doclose

Okay... it's really bed time

Woo Hoo #Liftworkshop is slightly cracked open... http://liftworkshop.com

Is this cool? ☄ ☠

Working with #Enthiosys Dan on #Bafo