Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. Remoting Vs Socket for high throughput scenario?

Remoting Vs Socket for high throughput scenario?

Scheduled Pinned Locked Moved C#
visual-studioquestionannouncement
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    devvvy
    wrote on last edited by
    #1

    Anyone tried exposing, say, a stock price update service (i.e. Price Feed), via Remoting as supposed to traditional tried and true Socket based communication? Is Remoting fast enough? Viable alternative?

    dev

    S 1 Reply Last reply
    0
    • D devvvy

      Anyone tried exposing, say, a stock price update service (i.e. Price Feed), via Remoting as supposed to traditional tried and true Socket based communication? Is Remoting fast enough? Viable alternative?

      dev

      S Offline
      S Offline
      sourabhsorate
      wrote on last edited by
      #2

      Hellow dev, according my knowledge u should go for remoting instead of sockets. Ofcourse u can implement it thorough sockets as well as remoting but remoting gives u more flexibility. Remoting can also handle multiple calls so better is to use remoting.

      D 1 Reply Last reply
      0
      • S sourabhsorate

        Hellow dev, according my knowledge u should go for remoting instead of sockets. Ofcourse u can implement it thorough sockets as well as remoting but remoting gives u more flexibility. Remoting can also handle multiple calls so better is to use remoting.

        D Offline
        D Offline
        devvvy
        wrote on last edited by
        #3

        This is for a client server application where scenario: 5000 x 3 updates/min --> 15k updates per min per client Each update comes from server, published/push to subscribers on client workstation over corporate intranet. You done remoting in situation similiar to this? Is it fast enough? I don't think encryption is relevant as this need to be done (optionally) whether remoting or over socket.

        dev

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups