Profile_bird

Hey there! esjewett is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving esjewett's tweets.

Already using Twitter
from your phone? Click here.

esjewett

  1. @progrium Ever heard of a bank with an API? That might tempt me. Pretty UIs, not so important (though USAA is pretty great on that front).
  2. RT @kohlerm: reading @dpp 's long mail about the design philosophy of #esme on the dev list. Good stuff! << You can say that again.
  3. Great. Just spilled coffee on my MBP keyboard. Seems like it still bjoqjiewgojf23jvearkojsadfcc xvdsa
  4. @jboner I think it looks great :-) Trying to figure out if I have anything to use it on...
  5. Really really behind on catching up this morning. Might not get back to everyone until tonight. Horrors!
  6. On the flight back to MDW. Then out again to PHL tomorrow morning.
  7. Thinking I'm going to have to go see the Fantastic Mr. Fox (per @davewiner). That and I need to pack for tomorrow. Stat.
  8. Reading about Akka - combination of Actors and Software Transactional Memory - http://bit.ly/73ym68
  9. For a podcast with consistently bad audio quality (it's the call connection), the IT Management & Cloud podcast is a freaking huge file.
  10. Posted "What's the deal with JAX-RS and Lift?" - http://bit.ly/5b0HaB Stream of consciousness on JAX-RS research wrt #esme API
  11. @dakoller We don't currently have public API methods. We could though. Let me know if you want them and we'll discuss on #esme ML :-)
  12. @dakoller Cool! Yes, we need to have the discussion about our token auth method. Currently it's broken (see http://bit.ly/8jGBQy) #esme
  13. Just realizing Jira (at least the version at issues.apache.org) doesn't seem to support threaded comments. Also, I'm kind of a whiner.
  14. RT @jayrosen_nyu: No names, no links: Writers give themselves a pass and denounce the "information wants to be free" crowd http://jr.ly/p7yk
  15. Created some Jira issue sub-tasks for api2 stuff. Now doing (hopefully welcome) administration on Release 1.0 issues.
  16. @dakoller If you want something fixed or built, just let me know. You can create Jira "sub-task" of this issue: http://bit.ly/6QgOrm
  17. @dakoller Wow, very cool. Hopefully the tests will help stability and make it easier to avoid breaking your library! #esme
  18. Starting to write some specific Jira issues for future updates to the #esme api2 endpoint.
  19. (BTW - I just posted a patch that works around the issue OpenID was having and re-enables it. Sort of...) #esme
  20. @kohlerm @yojibee OTOH, Lift request pattern matching seems to be able to do a lot of what JAX-RS does. Maybe all? Need to read more.