Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

FBN client side classes (Itinerary, Segment, Flight)

 
Yan Zhou
Ranch Hand
Posts: 137
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi there,

With the FBN assignment, the domain model shows Itinerary, Segment and Flight.

It seems that there need to be something equivalent on Client side as well, because we would not want to send clients a chain of objects when they are only interested in some properties of these objects.

I am thinking there has to be a FlightSpecification class since client class does not need to know that Flight has links to Equipments, etc., in other words I do not think we should expose Flight's server side functionality to client.

The question next is do I need to create client side classes for Segment as well? If not, where do I place info. regarding Itinerary and Segment for clients? There has to be a class to hold such info. Since Segment has links to server side Flight, I wouldnot want to send Segment to client, either.

What does everyone else think?

Thanks,
Yan
 
Gabriel Claramunt
Ranch Hand
Posts: 375
Monad Scala
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As an architect, you should be familiar with the J2EE design patterns (particularly with the VO/DTO pattern)
;-)
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic