On Friday, March 14, 2003, 11:50, Allie Martin wrote: MO>> or that the files are stored _and_ processed remotely which would MO>> mean only the relevant information is sent to the client, not the MO>> entire message base.
> What do you mean by relevant information? What I was hoping for was a setup where the client is merely a display of what's going on at the server side, like with Microsoft's Terminal Server. Then, if the client caches the message bases locally and updates both at the server and the client sides or if it is just a simple display does not matter to me, what does matter is that the entire message base does not have to be transferred over the WAN every time I, for example, purge and compress. > When you change the installation B's account home directory to that > of one on the server, no message bases are copied over. Installation > B will work with the bases and tbi files on the server. I understood, but that's exactly what I don't want. I wont the installation B to tell installation A what to do. Again, like Terminal Server. > But then again, you said you wish to have the tbb and tbi files > locally, which is everything and not just relevant information. My fault, I was doing other things while writing this mail, apparently I didn't get it all together at the end :-) -- Regards, Marcus Ohlstr�m Using The Bat! v1.62/Beta7 on Windows 2000 5.0 Build 2195 Service Pack 3 PGP Public Key at http://www.canit.se/~marcus/pgp.asc ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
