• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

B&S Overwriting Contractor Booking

 
Chris Bicnal
Ranch Hand
Posts: 99
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi everyone,

I've got a quick question about how people are designing their clients to work in a multi client environment.

Let's say we have two clients, client A and client B.
Client A performs a search.
Client B performs the same search.
Client A books record 1, eveything is fine.
Client B decides they want to book record 1....what happens?

At the moment (in my application) Client B will just overwrite the previous booking providing no warning or indication to the user. My client doesn't re-read the record when the booking is requested to see if it has changed.

I couldn't see any requirements for this behaviour in my specification (B&S 2.2.1) but I'd be interested to hear what other people have done about this issue.

Thanks,

Chris
 
Jevgeni Zhukov
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Chris Bicnal:

Let's say we have two clients, client A and client B.
Client A performs a search.
Client B performs the same search.
Client A books record 1, eveything is fine.
Client B decides they want to book record 1....what happens?


You should show some kind of message that the record is already booked and not overwrite the previous booking. The system will be useless if a booked record can be overwritten by any other client.

[ September 25, 2008: Message edited by: Jevgeni Zhukov ]
[ September 25, 2008: Message edited by: Jevgeni Zhukov ]
 
Iván Párraga
Ranch Hand
Posts: 54
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Two things here:
- I've implemented a "real" MVC, so all the changes produced in the server are notified to all the clients and they see these changes in real time. So, if I remove a record in client A, client B sees how this record vanishes from his view
- When invoking any use case, I lock the involved record, so if client B opens the modify view for record R1, client B only can see R1 but not modify or remove it

Cheers,

Iv�n
 
Chris Bicnal
Ranch Hand
Posts: 99
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the info, it looks like I'm going to have to put some logic in there to accommodate this situation! :-)

Ivan, I like the sound of your implementation - very cool!

I've gone for the n-tier approach rather than MVC. I feel it scales better and will be more suited to the web environment B&S want to eventually migrate to, although my clients are going to have to put up with an error message instead of fields that change magically before their eyes!

Chris
 
Jethro Borsje
Ranch Hand
Posts: 100
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am showing my users an error message when they try to book a record which already has been booked in the mean time.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic