I think the two technologies work well, we don't want to deal with crossdomain policy file issues so we deployed openAMF to a server and it calls the webservices, flash talks to 1 point in the system over remoting and that point then talks to all the webservices. If your business logic does not need to be exposed as a webservice then you can just have flash talk to your remoting gateway to an application component which will then call your business logic. We do a lot of services that have to be consumed by java or net and flash so we tend to create webservices, in flash with then create a "central" entry component that has the remoting gateway and it does the "logic" for the flash application and delegates busines to the business components.
For .net I'd look at flashorb's new freebie... I'm using flourine right now for .net but will also evaluate the flash orb one. Grant > Gavin Lilley wrote: > > > > >Due to changes beyond my control, I am now working on a M$ .NET/MSSQL server > >and need to migrate my old php/mysql code over. The php code includes AMFPHP > >Remoting classes. > > > >I am looking at either porting the classes into ASP Remoting or creating a > >set of wsdl Web services. > > > >Can anyone give me any insight into why they would use one technology over > >the other please? > > > >I have read that the two technologies combined work well, I dont understand > >this as I see a web service as an alternative to remoting - am I missing > >something here? > > > >-- > >Gavin Lilley > >_______________________________________________ > >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
