To add just a little color to this, I use java on the server side, but
POJOs are useless to me because I return almost all my data as
ResutSet/RecordSet's. There are a variety of reasons for this
including the pageablerecordset capability, but the bottom line is
that's how I do it. Rewriting the old recordset code that supports
AMF1, to me, is not at all sensitive to the needs of the developer
base. And again, we don't even know if its possible.
Matt from Adobe just said that he does not expect to be breaking
anyone's workflows, but I am not sure if that just meant Brian, who is
using Cold Fusion, but not FlapFlap since he is using AMFPHP. Given
that PHP is currently the most popular server side tool in the world
some statement of support for AMF1 would be helpful.
But there are others that think that since AMFPHP is an open source
"hack" and that Adobe has no obligation to maintain API compatibility
or continuity with any existing protocol. Instant deprecation is no
problem.
If this is Adobe's position on this issue and to open source in
general - or not, I would love to hear it directly from Adobe in
clear, no nonsense terms.
Therefore, if any Adobe management is listening, and if appropriate,
just detach the below letter, sign and return. I will forward to the
appropriate constituencies.
<snip>
-----------------------------------------------------------------------------------------
December 16, 2006
From: Adobe
To: Open Source Community
Non Cold Fusion/FDS users
PHP Users
RE: The needless breaking of your existing server communication solution
Screw You.
Warmest Regards,
___________________________________________
Signed Adobe Management Team
------------------------------------------------------------------------------------
<snip>
On 12/15/05, Brian Lesser <[EMAIL PROTECTED]> wrote:
> Hi Dave,
> This thread started with a query regarding using the open source AMF PHP
> software that a number of people have been using for some time to build
> Flash/AMF/PHP based applications. Developers in that space naturally
> want to continue to use the server-side code base (in PHP) they have
> been building out along with the new standalone Flex 2 IDE and AS3.
> However, it appears from the Alpha, and from what I gather Mike has been
> saying, that this will not be possible without reinventing a number of
> AS3 classes such as RecordSet from scratch. Perhaps worse, though I am
> not into PHP, is that it may not be possible at all if any code relied
> on the NetConnection.addHeader() method. This useful, public, and
> documented method of the NetConnection class has not been implemented
> and is still under discussion within Adobe. So, unless I'm missing
> something in what you wrote, I don't think it is reasonable to suggest
> PHP developers simply switch to using Web services and Java POJOs.
> I always understood that something like AS3 would to some degree have to
> break AS2 and AS1 code and that at some point a new document object
> model might break many APIs. But I do not believe Adobe has to
> completely break everyone's Flash Remoting applications from end to end.
> I sincerely hope that NetConnection.addHeader reappears in the beta. I
> also hope that if Adobe doesn't do it, someone else will come up with a
> solid AS3 RecordSet implementation that works flawlessly. I wish I knew
> for certain if that was even possible.
> I also think this discussion should give everyone pause. Imagine it is
> 20 months from now. Perhaps, like the ill fated Flash Remoting Gateway
> Servlet MM tried to sell at $999/CPU, the essential parts of Flex Data
> Services will be reverse engineered and available as open source for a
> number of different server-side technologies. Will Adobe once again
> rewrite everything to make it better and in the process break all its
> public APIs? Will every Java developer be left wondering if Adobe is
> just trying to remonetize AMF or if they just don't have the
> financial/developer resources to retire an API gracefully?
> In any case, some caution about breaking third party developer's
> applications from end to end seems appropriate.
> Yours truly,
> -Brian
>
> Dave Wolf wrote:
>
> >I don't understand why you can't simply use <mx:WebService/> to
> >replace <mx:RemoteObject> in most cases. Using AXIS you can use the
> >exact same POJO you might have used in a <mx:RemoteObject/> and do so
> >without the need for any gateway.
> >
> >-
> >Dave Wolf
> >Cynergy Systems, Inc.
> >Macromedia Flex Alliance Partner
> >http://www.cynergysystems.com
> >
> >Email: [EMAIL PROTECTED]
> >Office: 866-CYNERGY
> >
> >
> >
> >
> >--- In [email protected], hank williams <[EMAIL PROTECTED]> wrote:
> >
> >
> >>As far as I know there is not yet.
> >>
> >>There was some discussion about this on the flashcoders list when
> >>flex2 came out. I made a pretty big deal about the fact that the docs
> >>seem to indicate that standard remoting will not be something that is
> >>supported.
> >>
> >>Mike Chambers (a MM employee) indicated that it was supported. But
> >>what he meant was that it was supported at a super low level and you
> >>would essentially have to write all the low level remoting code for
> >>this.
> >>
> >>It seemed pretty clear to me that their intent was to, ahem,
> >>**encourage** remoting users to buy cold fusion or Flex Data Services,
> >>in order to do painless remoting, and that they were essentially
> >>orphaning anyone who was not doing remoting with one of their pricey
> >>gateways.
> >>
> >>Now, perhaps this post will bring adobe employees out of the woodwork
> >>crying foul and saying I am wrong. But the fact that there is any
> >>ambiguity about this isssue, is, in and of itself, a real problem.
> >>
> >>The fact that that there is not some strong statement of continued
> >>**full** support for traditional remoting is, to me, shameful.
> >>
> >>Regards
> >>Hank
> >>
> >>On 12/15/05, Flapflap <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>>Hi there,
> >>>
> >>>Because RemoteObject isn't available on Alpha is there a way to
> >>>
> >>>
> >use flex
> >
> >
> >>>2 with amf php ?
> >>>
> >>>Thanks...
> >>>
> >>>By the way : Hello World !
> >>> I'm new to this list.
> >>>--
> >>>Flapflap
> >>>
> >>>
> >>>--
> >>>
> >>>
> >>>
> >>>
> ______________________________________________________________________
> Brian Lesser
> Assistant Director, Teaching and Technology Support
> Computing and Communications Services
> Ryerson University
> 350 Victoria St.
> Toronto, Ontario Phone: (416) 979-5000 ext. 6835
> M5B 2K3 Fax: (416) 979-5220
> Office: AB48D E-mail: [EMAIL PROTECTED]
> (Enter through LB66) Web: http://www.ryerson.ca/~blesser
> ______________________________________________________________________
>
>
>
>
>
>
>
> --
> Flexcoders Mailing List
> FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
> Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
> Yahoo! Groups Links
>
>
>
>
>
>
>
------------------------ Yahoo! Groups Sponsor --------------------~-->
AIDS in India: A "lurking bomb." Click and help stop AIDS now.
http://us.click.yahoo.com/9QUssC/lzNLAA/TtwFAA/nhFolB/TM
--------------------------------------------------------------------~->
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
