StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POAndroid; are there any disadvantages to using XML parsing frameworks over SAX/DOM?
primarykey
Id
3863480
data
AcceptedAnswerId
3864220
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-10-05T12:11:33.907
FavoriteCount
0
LastActivityDate
2010-10-05T15:29:45.827
LastEditDate
LastEditorUserId
0
OwnerUserId
155695
ParentId
0
PostTypeId
1
Score
0
ViewCount
361
LastEditorDisplayName
text
Body
I'm experimenting with REST and XML on an Android application, primarily to create a REST client For handling XML returned from a given REST service, I'm tempted to use a simple framework such as <a href="http://xstream.codehaus.org/tutorial.html" rel="nofollow">XStream</a>. This allows me to easily map an object onto XML and vice versa, it doesn't come with the memory overhead like DOM, and requires considerably less coding that SAX Can anyone offer any disadvantages to going down such route?
Tags
<android><xml><rest>
Title
Android; are there any disadvantages to using XML parsing frameworks over SAX/DOM?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJimmy
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
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.