wcf - Server Architecture of Real-Time Updates App -


I am creating a stock ticker which requires continuous real time updates Network speakers with WCF 4.5 Javascript on the client, which introduced support for WebSockets.

Users' feeds vary widely; for example, many users adhere to popular large caps like FB, GOOG and MSFT, but each user follows several other "niche" shares which are for them Can be unique.

We all know that some options are refreshing the browser in real-time.

  1. Polling Professionals: Easy implementation Cons: Primitive, primitive, do not scale the waste bandwidth and chakras.

  2. Long time voting professionals: skilled, scalable. Cons: Old?

  3. WebSocket Professionals Efficient, scalable Opposition: Nobody can think that they support them as the most modern browsers.

    Can anyone choose anything more than 3?

    3. With, how is the track of open connection of the server kept? For example, if we design such that we maintain a pool of FB "followers" (i.e., customer connections interested in change in value of FB), then we know that when the price changes, So how is this pool maintained? From a service that keeps running in memory? In addition, if an FB follower closes his or her browser, does the service need to capture this event and update FB's follower pool? This is where I get fuzzy quickly.

    Check out this post about the hard sides of long posting:

    < P> How is the track of open connection of the server kept?

    Perhaps there is a way to connect and disconnect in WCF websacettes, if not, should definitely keep an eye on other frameworks I took a look at WCF websites some time ago, and Nothing looks like what I would like to use, by putting aside one, you will need Windows 8 or Windows 2012 to use it.

    You should like websites just and closing points, you should develop your stock ticker software with an event-driven architecture approach, and then provide an end point to receive / obtain the event, Which will be a totally different part of the app. I advise you for event management.

    When you have this clear, you can determine how the user will engage with your service and interact with it. In the architecture operated by web events, websites make great sense because it has full duplex, constant connection and widely supported web standards.

    To provide web cachet to .NET, WCF is not the only option, and it may not be best to add a websocket endpoint to your architecture, I recommend you use the webcott There is a very small component to provide the capability (Disclaimer: I have developed it), or if you want a more complex solution that does many things. See this example made with XSocket.NET:

Comments

Popular posts from this blog

ios - Adding an SKSpriteNode to SKScene from a child SKSpriteNode -

Matlab transpose a table vector -

c# - Textbox not clickable but editable -