[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework

Architecture Question

Tom

2/20/2008 4:50:00 PM

Hello,

I have a Windows form application that currently uses a database local to
the machine it is running on. We are planning on setting this application
up for a multi-user environment, so I would like to change to a 3-tier
architecture application for scalability:

1. My Client
|
2. My Business Logic Server (The client connects here)
|
3. My database server

We may also create another web form client in the future, and I would also
like that to connect to the business logic server as well.

My question is, what type of communication do you guys recommend between the
exist client and the business logic server?

1. If I use .NET remoting, can an ASP .NET page easily utilize the .NET
remoting code if I create an additional web form in the future?

2. If I setup the logic server to provide web services to clients, I have
heard that web services don't support transactions across multiple database
servers, so if I can't use web services, what should I use?

Any help is greatly appreciated. Thanks.
-- Tom

5 Answers

sloan

2/20/2008 7:39:00 PM

0

This post is a DUPLICATE.

There is a 1:18 PM Post (a few hours after this one).

............

I've made a reply there




"Tom" <tom.smith.123@hotmail.com> wrote in message
news:A503C4A4-3F48-45D1-8000-97E092A6BFFF@microsoft.com...
> Hello,
>
> I have a Windows form application that currently uses a database local to
> the machine it is running on. We are planning on setting this application
> up for a multi-user environment, so I would like to change to a 3-tier
> architecture application for scalability:
>
> 1. My Client
> |
> 2. My Business Logic Server (The client connects here)
> |
> 3. My database server
>
> We may also create another web form client in the future, and I would also
> like that to connect to the business logic server as well.
>
> My question is, what type of communication do you guys recommend between
> the exist client and the business logic server?
>
> 1. If I use .NET remoting, can an ASP .NET page easily utilize the .NET
> remoting code if I create an additional web form in the future?
>
> 2. If I setup the logic server to provide web services to clients, I have
> heard that web services don't support transactions across multiple
> database servers, so if I can't use web services, what should I use?
>
> Any help is greatly appreciated. Thanks.
> -- Tom
>


Tom

2/20/2008 8:45:00 PM

0

Thanks sloan. I'm newsgroup challenged. I'll reply to your other message.


"sloan" <sloan@ipass.net> wrote in message
news:uMZG9f$cIHA.5900@TK2MSFTNGP02.phx.gbl...
> This post is a DUPLICATE.
>
> There is a 1:18 PM Post (a few hours after this one).
>
> ...........
>
> I've made a reply there
>
>
>
>
> "Tom" <tom.smith.123@hotmail.com> wrote in message
> news:A503C4A4-3F48-45D1-8000-97E092A6BFFF@microsoft.com...
>> Hello,
>>
>> I have a Windows form application that currently uses a database local to
>> the machine it is running on. We are planning on setting this
>> application up for a multi-user environment, so I would like to change to
>> a 3-tier architecture application for scalability:
>>
>> 1. My Client
>> |
>> 2. My Business Logic Server (The client connects here)
>> |
>> 3. My database server
>>
>> We may also create another web form client in the future, and I would
>> also like that to connect to the business logic server as well.
>>
>> My question is, what type of communication do you guys recommend between
>> the exist client and the business logic server?
>>
>> 1. If I use .NET remoting, can an ASP .NET page easily utilize the .NET
>> remoting code if I create an additional web form in the future?
>>
>> 2. If I setup the logic server to provide web services to clients, I
>> have heard that web services don't support transactions across multiple
>> database servers, so if I can't use web services, what should I use?
>>
>> Any help is greatly appreciated. Thanks.
>> -- Tom
>>
>
>

Cowboy

2/21/2008 8:51:00 PM

0


"Tom" <tom.smith.123@hotmail.com> wrote in message
news:A503C4A4-3F48-45D1-8000-97E092A6BFFF@microsoft.com...
> Hello,
>
> I have a Windows form application that currently uses a database local to
> the machine it is running on. We are planning on setting this application
> up for a multi-user environment, so I would like to change to a 3-tier
> architecture application for scalability:
>
> 1. My Client
> |
> 2. My Business Logic Server (The client connects here)
> |
> 3. My database server
>
> We may also create another web form client in the future, and I would also
> like that to connect to the business logic server as well.
>
> My question is, what type of communication do you guys recommend between
> the exist client and the business logic server?
>
> 1. If I use .NET remoting, can an ASP .NET page easily utilize the .NET
> remoting code if I create an additional web form in the future?

Yes, but I would not head this direction. Better to use WCF (.NET 3.x) and
set up a "web service". You can more easily change the transport this way.
This gives you the best of both worlds: speed and simplicity.

> 2. If I setup the logic server to provide web services to clients, I have
> heard that web services don't support transactions across multiple
> database servers, so if I can't use web services, what should I use?

Hold on a second here.

If you send a complete message, you can span multiple databases. The web
service, in this instance, is just a messaging interface. Realize, of
course, that any transactions spanning databases are difficult, no matter
how you link them.

If you mean you cannot call multiple methods (on possibly multiple web
services) and have them linked in a single transaction, you are correct.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|
*************************************************


Commodore Decker

11/28/2011 5:44:00 PM

0

On 11/26/2011 09:27 AM, Phlip wrote:
>> That we went to Iraq for oil is a lie.
>
> During the riots we triggered the first week we took Baghdad, what was
> the only Ministry - nearly the only property anywhere - our troops
> defended?

What is global security for $100, Alex?

RichTravsky

11/30/2011 3:51:00 AM

0

Vandar wrote:
>
> 6322 Dead, 1465 since 1/20/09 wrote:
>

> >>That we went to Iraq for oil is a lie.
> >
> >
> > Then just WHY did America attack, invade, and occupy Iraq?
>
> "Occupy". Cute.
>
> We invaded Iraq to gain a military foothold in the heart of middle east

Lie. We already had access to Kuwait, Saudia Arabia, and of course, Israel.

> from which to launch further campaigns against Iran and Syria (remember
> the "Axis of Evil"?).

Yeah - wotta laff that was. Another lie.

> That's why we didn't finish Afghanistan before focusing on Iraq. We
> installed a US friendly government in Afghanistan and then Bush, like a
> fool, turned to Iraq.
> Now pull out your maps. What's between Afghanistan and Iraq. <gasp>
> That's right... Iran.

You mean Pakistan.

> And on the other side of Iraq, we find a border with Syria. What a
> coincidence. And what's on the western border of Syria?... Well, I'll
> be! It's Israel.

Yes, and? Is this supposed to mean something?

> Those plans fell apart because the knuckleheads in DC couldn't run a war
> to save their lives. They failed to expect such a large and lasting
> insurgency and were never able to establish that foothold.

You admit republicons are idiots and should not be trusted with power again...

RT