By bandwidth I didn't mean latency, I meant literraly bandwidth. I don't want to download masses of conversation scripts from the server at the start of the client. I could do this of another server via webstart if I stick it in jars and package it with the client.
Tbh, I hadn't even considered the processing of the conversations, but thats another good reason to put it on the client yep.
The three threats mentioned:
a) Someone supplying a particular option before they'd have chance to.
b) Someone reading the full conversations and getting an unfair advantage
c) Reading the conversation and getting info that should be available.
seems to cover everything I was worried about. I like the idea of sending the chain. That seems to cover that problem fairly neatly.
I had considered encrypting the conversations in someway but I don't know much about it.
In all honesty, I guess I was just looking for pros/cons for either solution, which I've neatly recieved