OK, obviously code won't write itself. Must start somewhere.

Do #Tags behave differently inline?

Sure...

SE76 SAPMSSCG SAPscript: Form Translation (from http://www.easymarketplace.de/transactions-p-t.php)

The JDI combines the functionality of Change Management Service (CMS), Design Time Repository (DTR), and Component Build Service (CBS).

To know how many users are viewing and maintaining a particular transaction use transaction ST03

OK, some sample text for @dickhirsch

Yeah! Posting status updates works from Twitter API with the following caveat: some clients don't update new message in timeline correctly because of incorrect message id.

Twitter API first version is ready. Prefix URL Path with "twitter", use token instead of password. More details to follow in the mailing lists- when I get some sleep :)

There are some performance tests, check the ESME blog. It's designed to be Scala-ble (pardon the pun).

Ouch: http://lampsvn.epfl.ch/trac/scala/ticket/1652

yeah, I got that too, it occurs only when you "restart" the action though (when you uncheck and check it).

Will do, waiting for son to fall asleep :)

@rhirsch Won't send to the "old" esme (esme.us) because of a bug in the stateless send_msg API call.

@rhirsch For resending to ESME, try http://esmehost/api/send_msg token=XXXX&message=say something

Is there going to a second "late" scrum call?

Documented new hooks and actions. Check out http://cwiki.apache.org/confluence/display/ESME/Actions

One known bug with the RSS feed: if it doesn't contain a pubDate field, ESME will post the item as a new one on every update, flooding your timeline.

Which wiki do you want me to document stuff now? The quick tips on the actions view and the mailing lists should give you some tips until I'm done.

Finished merging hooks-actions into trunk. Brace yourself, it's a huge chunk of changes.

Anyone know the difference in wiki.apache.org and cwiki.apache.org? What purpose do both of them serve?

Tonight I'll merge hooks-actions into trunk. I just wanted to have some documentation in place so people are not at a loss about the changes.

Just noticed the scrum starts in a minute :)

I figured out what Swampland is... check the liftweb Google group ;-)

OK, cancelled. I'm fine with any day, but the hour could be a problem. A start 5-7 GMT would suit me fine.

Soo... the Sprint today is postponed to Tuesday, or...?

Well, the REST(ful?) API works :) and the current UI might not look great, but you can see the messages. Good thing my changes had nothing to do with the UI...

Woohoohoo, merge done (huge stone off my chest)! Hooks-actions branch now in apache svn as well. Anyone interested in trying it? Please? :)

Found out that I won't be able to participate in the call tomorrow :(

Hmm. Breaking changes make it harder to include basic authentication for feeds. I guess it's now harder to merge the hooks-actions branch into ESME as well.

Check out the hooks-actions branch again, the Rss and Atom feeds were overhauled and are now more robust.

Unfortunately no, the branches are not merged yet, owing to the lift changes, pending move to apache, upcoming Christmas and whatnot :) but the branches should be very easy to merge since they have almost no overlapping changes.

@daniel I've fixed up RSS last night, tonight probably Atom will work as well.

I've updated to the latest lift changes in hooks-actions branch. Seems to be correct, if anyone's in a hurry, try it there.

Other breaking changes in Lift cause compilation of Boot to fail.

Got it: the feed is missing the optional elements pubDate (for RSS) and published (Atom), and my naive feed parser is not entirely robust. Will fix, thanks again!

@daniel Thanks for the feedback! I'd like to know more details: what feed url were you using?

@daniel If you're impatient, you can check out from svn. For info on how to use it: http://groups.google.com/group/esme-dev/browse_thread/thread/c4516c1d590f490d

Maybe I should look at how laconi.ca implements the Twitter API...

OK, only about half of the Twitter API are relevant for ESME. Now not sure how to indicate a "Method not implemented" either.

Just frustrated that the return structure is not specified anywhere- the XML/JSON format can only be explored by trying. And no DTD either.

@dickhirsch Oh, I know it all right... According to Google, it was viewed 20 times already, and that doesn't include the original Google Groups topic it was based on.

The difficult thing with the Twitter API will not be the *request* format, but the XML/JSON response format. I don't see this documented anywhere.

Wondering if I should work on Twitter API as a branch again.

@daniel Not sure, I think @dhague is working on evaluating/merging the branch.

Any objections if I start experimenting on the Twitter API? Twitter compatibility was one of the priorities, right?

Actually the hooks-actions branch of ESME already implements fetching Atom/RSS entries and posting to your message stream.

Is anyone working on the Twitter API?

@dickhirsch Time for the first easter eggs maybe? :)

Dedicating the new hooks-actions branch to my son, who officially has his first birthday now!