StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POData Encapsulation and Data Flow in PHP
primarykey
Id
9116838
data
AcceptedAnswerId
9117205
AnswerCount
1
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2012-02-02T17:21:27.407
FavoriteCount
0
LastActivityDate
2012-07-12T16:53:19.133
LastEditDate
2012-07-12T16:53:19.133
LastEditorUserId
367456
OwnerUserId
468592
ParentId
0
PostTypeId
1
Score
0
ViewCount
700
LastEditorDisplayName
text
Body
I am rebuilding a website I run which provides tide tables. I am doing it with the Zend Framework and am attempting to make it as object oriented as possible. I have been thinking about the flow/process that will occur when a visitor requests a tide table from a location and how it returns. I have come up with 2 different "types" of objects to use which will assist in this process. The first is basically a helper object that Zend Framework uses. The second is a data object (for lack of a better word) to encapsulate data that is passed between helpers. Here is a rough idea of the flow I am thinking about: <ul> <li>RequestHandler <ul> <li>Receives array for request from site controller or from api controller.</li> <li>Creates "data object" called QueryData and populates it with all information about the request.</li> <li>Passes QueryData object to LocationHandler.</li> <li>Returns the ResponseData object which was returned to it from the LocationHandler.</li> </ul></li> <li>LocationHandler <ul> <li>Receives QueryData object from RequestHandler</li> <li>Does work finding location and creates a LocationData object to store it in.</li> <li>Passes both QueryData and LocationData objects to different helpers such as TideHandler or WeatherHandler which return specific data for the initial query.</li> <li>Returns an array of ResponseData objects which contains the responses returned to it from each of the specific helpers (TideHandler,WeatherHandler,etc)</li> </ul></li> <li>TideHandler <ul> <li>Receives QueryData and LocationData objects from LocationHandler.</li> <li>Does work using data objects to find tide data. Creates a ResponseData object to store it in.</li> <li>Returns ResponseData to LocationHandler.</li> </ul></li> </ul> In doing everything this way I get a "plug and play" OOP approach that allows me to add to this much easier (I think?). Sorry for the long explanation leading up to my question... <h2>The Question:</h2> Is it common practice to encapsulate sets of data into an object (rather than an array) to be passed around to other objects which perform functions on it and send on new/modified objects? What are some other solutions or patterns that provide a similar level of functionality and flexibility?
Tags
<php><oop><design-patterns><object>
Title
Data Encapsulation and Data Flow in PHP
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. UShakre
UserOwnerUserId
1. USJeremy Harris
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.