RE: Why NOT the web?

[Pete Hall <pbhall@xxxxxxxxxxxxx>]

At 10:11 12/30/2004, Walden wrote:
> Pete mentioned having to lock everything that is read for update -- HUH?
> If I can read it w/o a lock on the iSeries why can't I on the web? As
> for data transfer rates, I assume we're looking at "local" machines
> since we're speaking of an ERP app. I would imagine it all 10MBit if not
> 100MBit ether, so rates aren't an issue. As for communication, why not
> simply use IBM's .NET provider? It's a native provider that seems to
> work well.

All I can tell you is that these are the things I've found to be problems 
over the last several years. You'll end up with the same data being updated 
simultaneously by multiple users if you don't have a mechanism in place to 
check the data out and enforce the lock, and you will have occasional 
performance problems if your network is substantial. A router or switch 
gets hit with a heavy load, or goes south for the winter, and suddenly 200 
users are calling the help desk. As far as .NET provider is concerned, I 
really can't say, although I distrust any product that could potentially 
update my host data without my knowing about it. Once you've developed the 
framework, it's easy to build a custom server, and it has about the same 
amount of overhead as running a batch job locally. There's no wasted 
motion, and it allows you to keep your business data secure. The only 
interfaces are the ones you define. It works for me. Your mileage may vary.


Pete Hall
http://www.pbhall.us