StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19001967
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-25T10:06:27.440
FavoriteCount
0
LastActivityDate
2013-09-25T10:06:27.440
LastEditDate
LastEditorUserId
0
OwnerUserId
748883
ParentId
19001459
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The Java Servlet API is an abstraction and defines the minimum requirements needed by any Java Web Application to handle any kind of request (if you look at it you will notice that almost all classes there are defined as interfaces or abstract classes). This API has been defined by the <a href="http://jcp.org/en/home/index" rel="nofollow">JCP</a> after a process in which different Java Server vendors (IBM, Sun, Apache, Oracle, etc.) agreed on the minimum requirements thus defining what is considered now as the official standard. However, the different vendors have different ways of implementing their servlet containers resulting in the diverse amount of them nowadays (each of them with different features). Since servlet containers need to keep track of both objects (the request and the response) to do a proper handling of both, they can't leverage the responsibility of creating a <code>ServletResponse</code> (or the HTTP variant <code>HttpServletResponse</code>) to the user - remember that what goes inside the Servlet's <code>service</code> method is user code. So, servlet containers create and prepopulate a request and response objects (using their own implementations) prior to invoke the <code>service</code> method. From the user point of view, just handling them through the interfaces is enough and this also protects vendor-specific code since we don't have access to the actual implementation of both objects. However, when the API was defined these vendors realised that, in some cases, the user would like to override the default behaviour of any of those objects so they included a set of wrappers (<code>HttpServletRequestWrapper</code>, <code>HttpServletResponseWrapper</code>, etc.) that can be extended by user code and used in either servlets or filters to replace the default implementations provided by the container.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAny good reason for passing ServletResponse as parameter?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAlonso Dominguez
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAny good reason for passing ServletResponse as parameter?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.