Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

GUI Search request to RMI Server via Controller

 
Aruna Raghavan
Ranch Hand
Posts: 194
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I am wondering if there is a need to make the call to the controller asynchronous.
Case #1: In the case of a search request, controller gets it, sends it to the data model which sends it to the Server. Controller blocks until a result set is received. It forwards the data to the gui by using tableChanged event.
Case #2: In the case of a booking request, some kind of a status comes back from the RMI server, depending on whether it's a good status or a bad status, Controller will call a method on the GUI to display the correct dialog box.
I don't see a need to implement special events like fireSearchResultsAreAvailable or fireBookingCompleted. In other words, the communication between the Controller and the GUI can be done just by table events or plain method calls rather than by using events ( especially in case #2, booking completed.)
Is this correct?
Thanks,
Aruna.
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I did just like you described. I did not use any asynchronistic method calling/Event processing. My client would wait for the results in both cases.
Mark
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic