Results 1 to 6 of 6

Thread: n-teir app design using .NET

  1. #1

    Thread Starter
    Super Moderator Wokawidget's Avatar
    Join Date
    Nov 2001
    Location
    Headingly Occupation: Classified
    Posts
    9,632

    n-teir app design using .NET

    If you were to have a DLL on a server and a client app running remotly, what method would u use to pass data between the tiers?

    MS Msg Queue?
    Dictionary Object (replacement for the property bag in VB6)?
    XML?

    Woka

  2. #2
    Your Ad Here! Edneeis's Avatar
    Join Date
    Feb 2000
    Location
    Moreno Valley, CA (SoCal)
    Posts
    7,339
    Probably Remoting or a Webservice. It also depends how remote the client is. Are we talking in the same LAN or over the Internet. Freewalls aside either solution would work although inside a LAN you have some different options as well. There is also the ability to Load assemblies from a remote location and have them update themselves but sometimes this can be harder than it sounds.

  3. #3

    Thread Starter
    Super Moderator Wokawidget's Avatar
    Join Date
    Nov 2001
    Location
    Headingly Occupation: Classified
    Posts
    9,632
    Not sure if it's a WAN or internet...there is talk of web services...when I say remote, I mean 200 miles away from the server, with an optical fibre connection to the internet me thinks

    Woka

  4. #4
    Your Ad Here! Edneeis's Avatar
    Join Date
    Feb 2000
    Location
    Moreno Valley, CA (SoCal)
    Posts
    7,339
    Then probably a WebService but remoting would still work. The WebService could provide the objects from the dll or pass a dataset to a local copy of the dll/objects.

  5. #5
    Banned
    Join Date
    Jul 2003
    Location
    New delhi
    Posts
    143
    you can take the help of webservices and WSDL



    actually web services give the facilty to achive com implemnt.

    with soap and http get.


    and u alos writing the code in wsl to make uddi connect

    Biswajit das

  6. #6
    Addicted Member
    Join Date
    Nov 2003
    Location
    India
    Posts
    227
    But the thing is, When you consider about webservices there will be a performance lack. Before moving your code to production, make sure that your code handles bulk transactions and web service is working fine. And you need to write lot of coding to maintain the state of the service.

    Performance wise you will feel better in Remoting, but the service should available only in your Intranet (Whereever it may be 200 miles or 2000 miles). In such scenario you can consider Remoting. Remoting supports various protocols.

    U can deploy your component in web with Remoting using HTTP protocol also. But there is no significance difference for a WebService & Remoting when you consider HTTP protocol. In this case WebService is the flexible one. If you use Remoting I suggest you to go for TCP Channel.

    -Jai
    Last edited by Jaiboy; Nov 27th, 2003 at 11:40 AM.
    See you,
    -Jai
    [Friends Never Say Good Bye]

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width