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. suggestions for calling webservice in windows service

suggestions for calling webservice in windows service

Scheduled Pinned Locked Moved C#
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.
  • R Offline
    R Offline
    ramyasangeet
    wrote on last edited by
    #1

    Hi all, I have created windows service which inserts data on timer basis. Right now am using dataconnections,queries in the windows service itself. Instead i can call webservice to insert data. I want to know whether which method works good. 1.using dataconnections in the windows service or Calling webserive for data insertion. Plz give ur suggestions Thanks in advance

    cheers sangeet

    R 1 Reply Last reply
    0
    • R ramyasangeet

      Hi all, I have created windows service which inserts data on timer basis. Right now am using dataconnections,queries in the windows service itself. Instead i can call webservice to insert data. I want to know whether which method works good. 1.using dataconnections in the windows service or Calling webserive for data insertion. Plz give ur suggestions Thanks in advance

      cheers sangeet

      R Offline
      R Offline
      Russell Jones
      wrote on last edited by
      #2

      if performance is important and if you are never likely to want to use that dataaccess code elsewhere then keep it in the service. If, however, the windows service is going to be one of many applications that will be using the data access layer and you want them all to use a consistent code base then use a webservice. It can be a hard choice to make. I have used both in the past according to requirements. I've also wrapped the data code into a dll and used the dll in different projects. No one solution will work for every case. RUssell

      R 1 Reply Last reply
      0
      • R Russell Jones

        if performance is important and if you are never likely to want to use that dataaccess code elsewhere then keep it in the service. If, however, the windows service is going to be one of many applications that will be using the data access layer and you want them all to use a consistent code base then use a webservice. It can be a hard choice to make. I have used both in the past according to requirements. I've also wrapped the data code into a dll and used the dll in different projects. No one solution will work for every case. RUssell

        R Offline
        R Offline
        ramyasangeet
        wrote on last edited by
        #3

        Thanks for ur quick response. In my case,am using the dataacces code only in the service and also performance matters. I think its better to use the dataaccess code in the service itself. Thank you.

        cheers sangeet

        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