Streaming data into Flex/Flash components via RPC?
Hi:
I'm looking for help in determining a mechanism for enabling my flash components to consume and display data from a streaming source. I know this sounds like a vague question, but I'm trying to wrap my head around the general process.
I'm assuming that I'll be able to connect external data producer via RPC.
The assumption is that we'd like the data to stream to the Flex app.
The app would in turn consume the data and display it in data bound components.
1) Is this possible?
2) What's the best approach for doing so?
3) Can you point me out to some additional resources for solving this?
Thanks,
JohnB
I'm looking for help in determining a mechanism for enabling my flash components to consume and display data from a streaming source. I know this sounds like a vague question, but I'm trying to wrap my head around the general process.
I'm assuming that I'll be able to connect external data producer via RPC.
The assumption is that we'd like the data to stream to the Flex app.
The app would in turn consume the data and display it in data bound components.
1) Is this possible?
2) What's the best approach for doing so?
3) Can you point me out to some additional resources for solving this?
Thanks,
JohnB
Siva Prasanna Kumar
yes your question is really open ended, it depends on many factors and components, for example a image referred using src="http://xxxxx.com/1.png" will stream and be loaded automatically.
ASKER
Yes, I apologize. The question is rather open ended.
I guess a good example would be the idea of streaming market data.
I'd like to make a connection (via RPC?) to our host server.
The channel would push streaming market data to the flex app.
I'd like the flex app to then display the data in the bound controls accordingly.
This is a different model then doing HTTP GETs.
JB
I guess a good example would be the idea of streaming market data.
I'd like to make a connection (via RPC?) to our host server.
The channel would push streaming market data to the flex app.
I'd like the flex app to then display the data in the bound controls accordingly.
This is a different model then doing HTTP GETs.
JB
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi:
Thanks so much for the link. This pattern certainly suits the approach that I had in mind. The specifics of the config file(s) setup and backend java class are just a little beyond me right now.
This will fit in with how we want to proceed. The notion is that we have an app containing 1 or more custom child components. The components are tied to the data via a topic context. The idea is to have 1 streamed update to which the Flex app would respond. Within the client, the app will use the context to determine which component will consume the data.
We will be pushing large volumes of data. A good parallel example of this would be the backend tied into a stock/equity feed (thousands of quotes/buys/sells per sec). Based on user requests, we would filter to return only pertinent data. I guess I have some concerns performance wise. We will be using AMF for the data coming over the wire, so this should help with some size reduction.
These notifications are asynchronous, so what happens if several "rounds" of pushes occur while the client is still responding to previous ones? Do these get queued up? At some threshold, do they fall off the table?
Do the same basic techniques apply to the latest release (4.0) of Flex/Flash?
Are there further optimizations available with the new release?
Thoughts?
Thanks again so much for a well written article.
JB
Thanks so much for the link. This pattern certainly suits the approach that I had in mind. The specifics of the config file(s) setup and backend java class are just a little beyond me right now.
This will fit in with how we want to proceed. The notion is that we have an app containing 1 or more custom child components. The components are tied to the data via a topic context. The idea is to have 1 streamed update to which the Flex app would respond. Within the client, the app will use the context to determine which component will consume the data.
We will be pushing large volumes of data. A good parallel example of this would be the backend tied into a stock/equity feed (thousands of quotes/buys/sells per sec). Based on user requests, we would filter to return only pertinent data. I guess I have some concerns performance wise. We will be using AMF for the data coming over the wire, so this should help with some size reduction.
These notifications are asynchronous, so what happens if several "rounds" of pushes occur while the client is still responding to previous ones? Do these get queued up? At some threshold, do they fall off the table?
Do the same basic techniques apply to the latest release (4.0) of Flex/Flash?
Are there further optimizations available with the new release?
Thoughts?
Thanks again so much for a well written article.
JB