Can you use Media Server 2 to PUSH just regular data to a SWF say like XML data sent every second?

THX

AFAIK... no. FMS has the same XML class as Flash, but I don't think you can
send complete XML messages to the clients. I suppose you could send the XML as
a string and let the player figure it out... but thats sort of sloppy.

Is there a reason you have to use an XML message? Perhaps using shared objects
or call/send mehtods might work.

Well I need to produce a visual representation of a horse race as it is
happening, so real time data needs to be sent each second. Thought about using
Flash Remoting but it is not a PUSH technology as far as I know? So what ever
is the best way to "broadcast" changing data to a swf?

Since you're just talking data, there are a number of ways you could accomplish
this. Here are a few:

1. You could use shared objects with FMS. With shared objects, the data is
updated to each client as it changes. You don't need to specify intervals
(although you can if you want.). If you are feeding data to FMS from an
external source, the clients can update as fast as FMS receives the data.

2. You could use Flex and Flex Data Services. Flex DS has the same ability to
establish a keep alive connection with the client and receive data as it
changes. I've never built a commercial application with Flex data services, so
I don't know what the license pricing is.

3. You could use remoting to have each client poll the server for updates on a
given interval. If you have a PHP backend to your get to your data you can use
AMFPHP (remoting for PHP), which is open source and free, and can run on a
shared hosting account if need be.

4. You could use LoadVars to poll the server for data on a set interval.

5. You can use an XML socket server to push data to each of the clients. The
downside here is that you might run into lots of firewall problems, as you'll
have to use a port above 1024 (flashplayer restriction)

If you can give me an idea of where your data is coming from and how many
users you might need to serve at any given time, I can make suggestions about
what the best option might be.

Wow, that's a really helpful list, thanks.

The app could eventually be viewed by say 100,000 web users watching a horse
race! So the most economical and efficent way of sening the data would be best
but also a server technology than can scale well is important too.

Thanks for all your help with this, much appreciated :-)

Kevin

With that many users, I would eliminate the server polling options I listed
above. That's would mean 100,000 request/reponses per update, and I have the
feeling that's going to bog down an http server pretty fast.

Serving 100,000 users would require an origin/edge FMS license and a number of
servers. I haven't asked for a quote on the origin/edge license, but I've read
that the price is upwards of $45k.

I'm thinking that the best solution might be an XML socket server. Although
you'll still need a number of servers and some good load balancing hardware,
the deployment cost will be quite a bit less.