inline On 8/29/05, Franklin Gray <[EMAIL PROTECTED]> wrote: > Binary remoting is faster then HTTP remoting, but there are times when > HTTP is required. I want to make sure I got this part right. > > 1) It is required when going through firewalls, correct (without opening > up dedicated ports)?
Not required but a lot easier > 2) Although not required, it is helpful to use HTTP remoting to utilized > the security functions of IIS, correct? Only if not going through a firewall, > > Our app will be running within our intranet. I'm not sure if that means > it's all within a firewall or not but I think it will be. Depends on the size of your company, ours has multiple home domains all seperated by firewalls so best to ask a network admin on that one. > > I used to use remoting for a DotNet client to a DotNet server through the > internet or in cases where the client couldn't access the DB server. If I > don't need to go through a firewall, then with the power of client > machines today and a lot of users of the system, wouldn't the application > run faster with having the middle-tier on the client machine assuming the > client can access the DB server (clients don't bog down the server's > memory)? The balance between cached central data and client side business logic, can only be decided on if you know how the company operates, we could give you ideas, but it comes down to the use of best fit for the schema and not a Recomended structure. imo. Davy J =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
