My First "Acropolis" Application
First, let me just say that the walk through for building an Acropolis application never actually tells you what the heck an Acropolis application really is. At this point, I'm still a little fuzzy on the entire concept myself. I assume the fuzziness will become more sharp and crisp as time goes by and I do more work with Acropolis.
Notice the italics. Somebody is talking to somebody.
REST's client-server separation of concerns simplifies component implementation, reduces the complexity of connector semantics, improves the effectiveness of performance tuning, and increases the scalability of pure server components.
Emily and SiteFlash are most efficient as REST architected frameworks although they can be adapted for any circumstance.
We'll leave it there and focus on a couple things. First, it can be done on Windows XP. Second, it reduces the requirements of "programming" and it would be a natural logical construct of the capabilities and uses described in the patents.
If Microsoft wants to fight, they will have to deal with people like IBM who've been working with this stuff since at least 2001 unless you believe tepe and legofeel.
Would Microsoft really risk all their future on a probable outcome facing the MSFT directors of the board on something like irule's description of Microsoft's situation in the SiteFlash Patent. And then there's another patent to fight over. I don't think we're looking at a Microsoft that's crippled and paranoid. This looks like a bold and confident integration for efficiency's sake rather than a construct for dodging the ball.