I am saddened by this situation... if you read a couple of posts on my blog you'll understand at least one of the reasons I left Adobe:
http://blog.jvroom.com/2009/12/11/understanding-the-market-for-software-platforms/ http://blog.jvroom.com/2009/10/29/tips-for-buying-and-selling-enterprise-software/ In terms of how to go forward for customers that can't afford the new license, has anyone seen the flex 4 license for fds.swc? That gets shipped with the Flex Builder data tools and unless they changed things since I left, contains the client half of the LCDS APIs. Maybe there are restrictions in how that code can be used though? It has the hardest part of the association implementation, offline, etc. in there. If you can use all of the client features, you could emulate the server parts you use on blazeDS or GraniteDS so you can move your applications over to a different infrastructure without having pay the big license fee and rewrite your client apps. Doing simple CRUD stuff using BlazeDS would be pretty easy, in fact you can do that with FB 4 's data management just not using the assembler interface on the server. That does not do sync, associations, change batching though. The two trickiest features in LCDS2.6 were auto-sync and RTMP. If you don't need those (i.e. manual sync and long-polling are ok), it is not a huge bit of server code to replace the rest since most of that is in BlazeDS. Are there enough affect customers out there that we should start a project around this? I'm in the middle of a pretty big project of my own and so don't have a ton of time but would be happy to chip in. Jeff On Thu, Jan 21, 2010 at 7:38 AM, busitech <[email protected]> wrote: > > > I'm curious how many of your projects were deployed into production using > the no-charge Single CPU (or the 100-user departmental) licenses of LCDS > 2.x. > > Since the release of LCDS 3.0, neither of these licenses exist. This leaves > our small business customers running in production using the Single CPU > license with no upgrade path going forward, unless they can come up with the > steep license fees for ES2. I doubt any of our customers will be able to > afford it. > > Needless to say, this seriously impedes our ability to do business on the > LCDS platform going forward in the SMB market we serve. It also leaves our > hands tied with respect to the software we've already developed and > deployed. BlazeDS is not an option - it would require a total rewrite of > client and server, and mass annihilation of features. > > How are these changes affecting your business? > > >
