I haven't given it much thought, but I'm not sure how HTTP caching would help in update activities in a REST environment, but it does seem that HTTP is much more vendor- and language-neutral than, for example, JMS. Mind you, I still think Sonic's messaging product is best-of-breed. But, as you have encountered with legacy big iron, you're not always operating in a JVM. Plus, and this has become more important the longer I've worked, text-based APIs are much easier to prototype and debug. Combined with a dynamic (a la scripted) language, you could prototype new operations in a jiffy.
Disclaimer This is a personal weblog. The opinions expressed here represent my own and not those of my employer. Vendors, journalists, fellow bloggers, etc. are NOT free to quote with attribution to my employer.
1 comment:
I haven't given it much thought, but I'm not sure how HTTP caching would help in update activities in a REST environment, but it does seem that HTTP is much more vendor- and language-neutral than, for example, JMS. Mind you, I still think Sonic's messaging product is best-of-breed. But, as you have encountered with legacy big iron, you're not always operating in a JVM. Plus, and this has become more important the longer I've worked, text-based APIs are much easier to prototype and debug. Combined with a dynamic (a la scripted) language, you could prototype new operations in a jiffy.
Post a Comment