Thanks for the info.
I got to agree with Syd in that other thread, things seem to have
gotten much more complex when it comes to Remoting. It was a lot
easier in Flash (and I always used CF for Remoting).
And why does the 'old fashioned' way seem to be deprecated? Is it just
to support AMF3?
I think this stuff still works:
var nc:NetConnection = new NetConnection();
nc.objectEncoding = flash.net.ObjectEncoding.AMF0;
nc.addEventListener(NetStatusEvent.NET_STATUS, onConnectionStatus);
nc.addEventListener(IOErrorEvent.IO_ERROR, onConnectionError);
nc.addEventListener(SecurityErrorEvent.SECURITY_ERROR,
netSecurityError);
nc.connect("http://localhost:8500";);
var responder:Responder = new Responder(ongetNameResult,
ongetNameError);
nc.call("cfc.flex.getname", responder);
To me that's much easier to follow. And no messing with XML and
destinations. Heck, I even set up a secure destination and got it to
work - but only because someone gave me good advice, I dread to think
how long it would have taken otherwise.
I guess my point is this: Adobe needs to make this simpler.
Stefan
On 22 Feb 2008, at 21:49, Douglas Knudsen wrote:
> Stefan,
> besides all these CFC issues/topics, the other piece of the puzzle
> on this
> thread was just discussed with closure on our local Flex UG list in
> Atlanta. You can see the posts here
> http://www.mail-archive.com/discussion%40affug.com/msg00688.html
> It talks of using Flourine, but the idea is the same.
>
> HTH
>
> DK
>
> On Mon, Feb 18, 2008 at 1:56 PM, Rick Root <[EMAIL PROTECTED]>
> wrote:
>
>> On 2/18/08, Stefan Richter <[EMAIL PROTECTED]> wrote:
>>>>
>>>> I know that. You don't have to prove it to me. The whole
>>>> purpose of
>>>> "remote" is really for web-services anyway.
>>>
>>> I only mentioned it because you stated:
>>> I prefer to use access="remote" so people can't call my
>>> CFCs via HTTP calls directly.
>>
>> Here's what I said:
>>
>>> The thing that bothered *me* about the default setup (above,
>>> including
>>> the comment) is that it allows any remote methods to be called as a
>>> web service. I prefer to use access="remote" so people can't call
>>> my
>>> CFCs via HTTP calls directly.
>>
>> Clearly my second sentence is in conflict with my first. What I
>> meant
>> is that I'd prefer to use "access=public" to prevent people from
>> being
>> able to call my CFCs via HTTP.
>>
>> But a suitable solution would be to just move them outside the web
>> root.
>>
>> Of course, in order to do that (via mappings) you have to enable that
>> feature in the remoting config
>>
>> <!-- Use the ColdFusion mappings to find CFCs, by
>> default only CFC files under your webroot can be found. -->
>> <use-mappings>false</use-mappings>
>>
>> Sorry for confusion in my statement.
>>
>> Rick
>>
>> --
>> Rick Root
>> New Brian Vander Ark Album, songs in the music player and cool behind
>> the scenes video at www.myspace.com/brianvanderark
>>
>>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;160198600;22374440;w
Archive: http://www.houseoffusion.com/groups/Flex/message.cfm/messageid:5026
Subscription: http://www.houseoffusion.com/groups/Flex/subscribe.cfm
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.37
