Thanks. I read through that , and it helps with retreiving, and databinding.
I cannot, however, find any doc, code, or examples that reference how to send
data update packets back to Coldfision, or .net from the Flash client. The
Trio example showcase on the site also conveniently leaves this updating data
piece out. Retrieving, and databinding is only half of the issue. The as2.0
code for sending new/changed data back to the serverside , parsing this XML
data packet in CF or .NET, and and then creating the appropriate SQL update
statements back to the database seems to be the missing part.
I find it truely unbelievable that Macromedia provides no end to end examples
that cover the use of V2 UI components, V2 client side remoting, and serverside
updating of data using Coldfusion and .NET.
proggirl - 18 Oct 2004 10:10 GMT
I agree that they need both more and better detailed examples of the new
components. I am hoping that they are in the works and coming soon.
As to using the new components with .NET, I know there are reasons to use
Remoting vs. Web Service etc. It also looks like you can remote a web service
with Flash Remoting. However, the big reason I would try and use just the Web
Service connector for .NET (even though you have to reveal your .NET code as a
webservice) is: 1) the examples seem clearer for that and 2) Flash Remoting is
built into ColdFusion so you can access it either way. However for .NET you
have to also buy Flash Remoting to put on your expensive Server 2003. That in
my mind is enough to in most situations do the web service component. It also
has a standardized protocol so if something non-Flash needs to access it can.
Just my opinion. It may change as I learn more.
Micah Caldwell - 19 Oct 2004 22:07 GMT
This has proven invaluable to me in teaching myself Flash Remoting
2.0. Included with many of the class API documents is short examples
on how to use them.
http://livedocs.macromedia.com/flashremoting/mx2004/actionscript_api_reference/f
rameset.html
I don't know if this is what you guys are looking for but it may prove
usefull. As for updating a database, from my reading online it seems
that everything needs to be taken care of serverside. You would make
a call to a service with the database changes as a parameter. Then
your service would compile that into a database query and send it to
the database. The database would return success/error to the service,
and then the service would send a modified success/error to Flash,
which would display the error to the user if needed.
> I agree that they need both more and better detailed examples of the new
> components. I am hoping that they are in the works and coming soon.
[quoted text clipped - 9 lines]
> has a standardized protocol so if something non-Flash needs to access it can.
> Just my opinion. It may change as I learn more.
CFFLDave - 23 Oct 2004 19:31 GMT
I agree with you. Remoting is expensive. That, and in addition to finding
virtually no good examples on V2 Remoting, I will poabably go with the web
services route. Have you found any good data binding and data connectivity
examples using web services. The one I found are usually not "end to end"
examples, and leave alot out?