LostProgrammer
Centurion
- Joined
- Jan 17, 2003
- Messages
- 123
Does anyone have any experience with Remote Objects in vb.net?
Please respond if you do.
Anyway, I have a r.o. that contains a db component. The db layer handles inserting/updating/deleting info in the database. If an error is thrown in the db layer and the transaction is rolled back, what should happen to the exception. Should it propagate back to the client or be handled server side? Should the client be notified that the transaction was not commited?
On server side, i could log it, email it, send to a message queue, but without the client monitoring a message queue they would never know the true reason the item was not commited to the database.
Of course, I could return Nothing from the remote object call, or a small message object but what is the 'best practice' in this situation?
Thanks for you help,
-lp
Please respond if you do.
Anyway, I have a r.o. that contains a db component. The db layer handles inserting/updating/deleting info in the database. If an error is thrown in the db layer and the transaction is rolled back, what should happen to the exception. Should it propagate back to the client or be handled server side? Should the client be notified that the transaction was not commited?
On server side, i could log it, email it, send to a message queue, but without the client monitoring a message queue they would never know the true reason the item was not commited to the database.
Of course, I could return Nothing from the remote object call, or a small message object but what is the 'best practice' in this situation?
Thanks for you help,
-lp