3 ms·
> It's a proprietary blob that Adobe controls. Check out a recent hot topic from the Adobe Flex mailing list. Basically the Adobe Lawyers rewrote the license
by wallflower 17y ago
> It's a proprietary blob that Adobe controls.
Check out a recent hot topic from the Adobe Flex mailing list.
Basically the Adobe Lawyers rewrote the license agreement for Flex (Flex being Flash that uses an integration server) - it now disallows trying to make any server of your own that talks the same language their now very $$$ (no single CPU option) integration server does.
"took a look at the FB4 Beta 2 License Agreement, and here's what I found:
2.4.7 Flash (R) Builder(R) with LiveCycle(R) Data Services(LCDS) Data Management Library. Your rights to this Software are limited. In order to (a) utilize the file called "fds.swc" (the "LCDS Library") to develop associations , (b) utilize the LCDS Library to develop offline capability, (c) use the application modeling plug-in, or (d) utilize the LCDS Library to develop a product that competes with LiveCycle Data Services or BlazeDS, you must obtain additional licensing rights from Adobe."
- cnunciato 17y agoThat's because LCDS is a commercial product. Flex itself is not (it's an open-source framework), nor is Flex simply "Flash that uses an integration server."
- wallflower 17y ago> (d) utilize the LCDS Library to develop a product that competes with LiveCycle Data Services or BlazeDS BlazeDS is their open-source version. So they are saying you cannot compete with our open-source version, either. Yes, I know Flex is not just Flash. A haiku I wrote while waiting for mxmlc: it's more than just flash enterprise level big apps not just eye candy