Originally posted by Luigi Smith:
Regarding question #1, I would choose servlets over JSPs for input validation, such as Struts does, unless you can use JavaScript, then I would favor that.
Agree, but have to add that if you use JavaScript its only an adition to server side validation to avoid server roundtrips with malformed data, because - as we all know - a user can turn out JavaScript or even manipulate the client-side validation which has been sent to the client.
Regarding question #2:
Latency is a more narrowly defined concept than just response time. I know correct definition is in my Fowler, Enterprise Architecture book. If I remember right, its waiting time for user due to network operations (serialization, de-serialisation of remote call).
I think:
a) is right, because interface has fewer methods from caller perspective(simpler)
b) is obviously right
c) I am not sure, but I tend to say that its wrong. You can simply add methods to the remote object. O.k. you will have to regenerate the stubbs and stuff. But with coarse grained objects, you will have kind of Data Transfer Object as a container for the transmitted data. So you have to change this DTO, when you want additional information to be responded from remote objects.
d) is wrong. The opposite is correct: Fine-grained objects result in increased latency for user actions.
[ January 06, 2004: Message edited by: Axel Janssen ]
[ January 06, 2004: Message edited by: Axel Janssen ]
