Mike,
I am not attempting to piss you off.
That said, this is not an issue just for me but almost everyone who is
going to attempt to do anything useful with this player, given that it
is designed as a connected player. It did not seem to me appropriate
to have a private conversation about something that pertains to almost
everybody. Given that you personally, categorically said that it
works, and given that you are the MM representative active here, it
makes sense to draw it to your attention. I do not believe I have
broken any protocol, notwithstanding your tone.
Thank you for clarifying the new semantics of the mx vs. flash mnemonics.
Regarding whether implementations are complete, this is a very good
point. I understand this is alpha. But needless to say remote access
is kinda important for connected apps. Most of us have existing
infrastructures that we could test on if we can access it. If you
really dont want us trying to do connected stuff yet perhaps that
should be an advisory.
Regards
Hank
On 10/19/05, Mike Chambers <[EMAIL PROTECTED]> wrote:
> Hi.
>
> First of all, if you need to direct an email to my attention, please
> email it to me, and not to FlashCoders:
>
> [EMAIL PROTECTED]
>
> second, as I posted earlier, remoting / AMF0 is supported in the Player
> (as Muzak demonstrated). AMF0 is not currently supported in the
> framework (AMF3 is).
>
> The mx.* packages are part of the framework. The flash.* classes are
> part of the player.
>
> This is an early ALPHA, so documentation and implimentations may not be
> complete.
>
> mike chambers
>
> [EMAIL PROTECTED]
>
> hank williams wrote:
> > Ok, so I am potentially back to my original position of being
> > concerned that remoting is not supported.
> >
> > Muzak did some work with the netConnection class, but in the "old
> > days" remoting worked by requesting a service from a NetConnection by
> > calling connection.getService("servicepath");
> >
> > There is no getService call documented in the actionscript
> > documentation, so my question is how does this work now?
> >
> > I am thinking it is related to the mx.rpc.remoting package, but the
> > documentation seems ah... scant.
> >
> > for the RemoteObject constructor is says:
> > --------------------------------------------------------------------------------------------------------------------
> > public RemoteObject(destination:String = null)
> > Creates a new RemoteObject.
> >
> > Parameters
> > destination:String (default = null) — [optional] Destination of the
> > RemoteObject; should match a destination name in the flex-services.xml
> >
> > --------------------------------------------------------------------------------------------------------------------
> >
> > but what is flex-services.xml. And if I am writing pure actionscript
> > why would I need to establish a flex-services.xml file either locally
> > or on a server.
> >
> > I ask this question because you (mike chambers) earlier today said we
> > could do remoting via actionscript without flex components and without
> > the flex enterprise services. So I am really just looking for the
> > equivalent calls to using netConnection and a netServiceProxy.
> >
> > Thanks
> > Hank
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Flashcoders mailing list
> > [email protected]
> > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>
> _______________________________________________
> Flashcoders mailing list
> [email protected]
> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
