Docs for request classes + refactor

Documentation for the content and search request classes.

There is no need for the request classes to inherit off a
base request class.  Currently the base class has limit and offset
fields, but if for example there is an image submission request class
the limit and offset become meaningless.

The content reply class should have a field for the content request
just like the search reply has  a field for the search request.

Change-Id: I8d9dfe8a31806c6bb3b31f66d1338c2999e27ce2
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>

1 files changed, 22 insertions, 0 deletions

diff --git a/src/location/places/qplacecontentreply.cpp b/src/location/places/qplacecontentreply.cpp
index e1d7462b..1deb6137 100644
--- a/src/location/places/qplacecontentreply.cpp
+++ b/src/location/places/qplacecontentreply.cpp
@@ -52,6 +52,7 @@ public:
 
     QPlaceContent::Collection contentCollection;
     int totalCount;
+    QPlaceContentRequest contentRequest;
 };
 
 QT_END_NAMESPACE
@@ -66,6 +67,9 @@ QT_USE_NAMESPACE
 
     \brief The QPlaceContentReply class manages a content retrieval operation started by an
     instance of QPlaceManager.
+
+    See \l {Fetching Rich Content} for an example on how to use a content reply.
+    \sa QPlaceContentRequest
 */
 
 /*!
@@ -129,3 +133,21 @@ void QPlaceContentReply::setTotalCount(int total)
     Q_D(QPlaceContentReply);
     d->totalCount = total;
 }
+
+/*!
+    Returns the content request that was used to generate this reply.
+*/
+QPlaceContentRequest QPlaceContentReply::request() const
+{
+    Q_D(const QPlaceContentReply);
+    return d->contentRequest;
+}
+
+/*!
+    Sets the content \a request used to generate this this reply.
+*/
+void QPlaceContentReply::setRequest(const QPlaceContentRequest &request)
+{
+    Q_D(QPlaceContentReply);
+    d->contentRequest = request;
+}