Today we’ve finally submitted chapter 6 of the book on Enterprise development with Flex to O’Reilly. This one was about advanced techniques of using BlaseDS in communications between Flex and Java. At this point you’d expect something like, “It’s coming out nicely”. Sorry guys, I’m not a modest person. But I’m honest.
Here me out: this chapter 6 (66 pages) on advanced techniques of Flex/Java communications using open source BlazeDS is a gem. This chapter alone is worth buying the book. Server side push over AMF, reverse side RPC, automatic data synchronization…
I have the best co-authors. Ever. They’re just amazing. Yes, we fight with each other. We don’t agree. We are not politically correct. We use the f-word when discuss enterprise architecture. We want to find the best possible solution for our customers. We publish thought provoking articles (some people call them controversial, but they are freaking wrong). But guess what, we’ve been there. And I’m not talking about sales presentations trying to convince you that Flex/Java does your body good. “Take a look… it’s just 20 lines of code and we populated the data grid with XML coming from the server”. It’s so sweet….
I’m talking about the real stuff that Wall Street is dealing with day in and day out. OK. Forget about Wall Street. They are still out of style. Let’s talk about the calls like this one, “We are going live in two months. Can you please take a look at our application it doesn’t perform that great.”
Oh, really….It doesn’t perform well? Don’t kid yourself. It’s dead in the water. I know, I know. You’ve outsourced the development. It seemed so easy to drag and drop Flex components… You didn’t get a chance to schedule stress tests yet? How many? Ten thousand users will play online roulette…? We’ll do our best.
I don’t know why O’Reilly decided to sell this book for stinking fifty bucks. We don’t have a say in pricing. But it should cost a lot more than that.
Sorry, I’m not a modest person, but at least I’m honest.