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. Moving Data Between Tiers

Moving Data Between Tiers

Scheduled Pinned Locked Moved C#
designbusinessxmlhelpquestion
4 Posts 4 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.
  • S Offline
    S Offline
    shambho
    wrote on last edited by
    #1

    I want to build a classic 3-tier application. I want the business logic layer to be fully independent of UI(i.e. it should work well for both windows and web applications well and good). How can i pass the data between the tiers. What are the options available. what about raw xml, dataset, serialized xml or serialized dataset.I would also like to know why I should use one technique over the other. Any help appreciated. Thanks in advance. anand

    C S 2 Replies Last reply
    0
    • S shambho

      I want to build a classic 3-tier application. I want the business logic layer to be fully independent of UI(i.e. it should work well for both windows and web applications well and good). How can i pass the data between the tiers. What are the options available. what about raw xml, dataset, serialized xml or serialized dataset.I would also like to know why I should use one technique over the other. Any help appreciated. Thanks in advance. anand

      C Offline
      C Offline
      Christian Graus
      wrote on last edited by
      #2

      The way you move the data is irrelevant. I'd move data in whatever form is easiest, i.e. when connecting to a database, I'd just return a dataset, unless only one value is called for. Christian I have drunk the cool-aid and found it wan and bitter. - Chris Maunder

      S 1 Reply Last reply
      0
      • C Christian Graus

        The way you move the data is irrelevant. I'd move data in whatever form is easiest, i.e. when connecting to a database, I'd just return a dataset, unless only one value is called for. Christian I have drunk the cool-aid and found it wan and bitter. - Chris Maunder

        S Offline
        S Offline
        sreejith ss nair
        wrote on last edited by
        #3

        hi, Lot of ways are there to move data to and fro to any layer. If it is a database related operation then we can persist the data in dataset or datatable. If it is some other requirement then you can go and change the accesability modifiers of feild or data members. My favorate way is, Encapsulate all logic into a .dll file and communicating through messaging.:) ************************** S r e e j i t h N a i r **************************

        1 Reply Last reply
        0
        • S shambho

          I want to build a classic 3-tier application. I want the business logic layer to be fully independent of UI(i.e. it should work well for both windows and web applications well and good). How can i pass the data between the tiers. What are the options available. what about raw xml, dataset, serialized xml or serialized dataset.I would also like to know why I should use one technique over the other. Any help appreciated. Thanks in advance. anand

          S Offline
          S Offline
          Salil Khedkar
          wrote on last edited by
          #4

          Make the three tiers like the a. The UI tier (ASP.NET Web based or C#.NET Windows based) b. The business logic (C#.NET Web Service) c. Storage tier (Database and file system) Between a and b the data will flow with the SOAP protocol in form of XML. This will allow third party clients like external systems, Unix based programs to connect with your software. Between b and c you need not worry about how data flows, let the ADO.NET classes take care of that. a never talks with c directly. Hope this helps. For more info read Web Services turorials, WS client tutorials and an ADO.NET book.

          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