Re: Designing .NET applications

Thanks for your comments Ben.

Logically, I prefer logic assembly in a server.

Web Services may be expensive for the type of application, and I think is
more service-oriented.

Remoting ¿? Could you get more information.

Imagine, you develop an object-oriented application, and business components
are in a server for two reasons:

1. Maintance. Only one copy.
2. the interaction between business process and database is running in
the server.
3. Potentially, you can reuse object in others platforms.

But, what technology o paradigme is needed to allow instances of objects,
created in the server by the client, where data object could persist (of
persistency) during all execution of the client. ¿?

Because I think that web services doesn't keep data: you ask some, it runs
the query and returns the result.

Thanks.

--
Rafael Gómez
Technical Project Manager
NewGen (Spain)


"Ben Kloosterman" wrote:

> Hi Rafael ,
>
>
>
> > It is not important if presentation and business layers are running in the
> > same client or business layer is running in the server, the most important
> > thing is when I need to offer a web-broser interface, only deploy the
> > interface and put my business objects in a IIS (for example).
>
> Actually this is critical in terms of maintenance. Do you distribute the
> same logic assembly to all desktops + a server ?
>
> I had a customer who thought he needed webaccess for remote users , instead
> we build a smart client and it works brilliantly . For larger sites i put
> business logic in a seperate Tier and access it with Remoting or Web
> services.
>
> If you feel comfortable with web services you could ensure all the clients +
> web communicatre through a common web service . This works well but you have
> to remember Web service calls are expensive so you dont want to make many
>
> Regards ,
>
> Ben
>
> "Rafael Gómez" <RafaelGmez@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:F9F5D394-11E7-4C5C-9ED1-EF8062144AC4@xxxxxxxxxxxxxxxx
> > Hi,
> >
> > I'm considering to develop a .NET application.
> >
> > I have read a lot about 3-tier model, n-tier model and distributed
> > application design, and conceptually I think I understand it.
> >
> > The goal of the design that I want is deploy business components one time,
> > to allow reuse its in windows forms application and ASP.NET application.
> >
> > It is not important if presentation and business layers are running in the
> > same client or business layer is running in the server, the most important
> > thing is when I need to offer a web-broser interface, only deploy the
> > interface and put my business objects in a IIS (for example).
> >
> > The problem occurs when you consider to implement it.
> >
> > What kind of technology I have to use to develop business components ?
> >
> > classes in the same project application, dll's, ActiveX...
> >
> > What Kind of comunication I have to use between presentation layer and
> > business layer to achieve de initial goal ?
> >
> >
> > Thanks in advanced.
> > --
> > Rafael Gómez
> > Technical Project Manager
> > NewGen (Spain)
>
>
>
.

Relevant Pages

  • Re: Designing .NET applications
    ... > Imagine, you develop an object-oriented application, and business ... > are in a server for two reasons: ... Web services should never be a thin layer over the DB, ... >>> same client or business layer is running in the server, ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: How to move ASP.NET app from one machine to two machines.
    ... I’m going to focus on Remoting with Web Services as a backup plan. ... Your UI layer is not a problem as all you ... > If your business layer contains components that you want on another server, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: interfacing with data layer
    ... This mechanism can sit between the Business layer ... If you have an "app server" that also hosts your data access code, ... have web services as the transport between web server and app (business ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: How to move ASP.NET app from one machine to two machines.
    ... If your business layer contains components that you want on another server, ... components into web services and have the web services and the business ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SBS2003 Partitioning
    ... It doesn't matter how small the business is it is a bad practice to sell a workstation for use as a server. ... Businesses come to rely on a server very quickly and within a matter of months may no longer be able to function effectively if the server goes down. ... There is no real advantage to moving the page file from the system partition in a small server with one drive/array, and yes it's a good idea to keep Exchange and SQL on separate partitions but given the size of drive you intend on using probably two partitions, at most three, is your best option. ...
    (microsoft.public.windows.server.sbs)
Quantcast