From e10cca676b6d8227e864d3cf0588b62714d90b01 Mon Sep 17 00:00:00 2001
From: gmantele <gmantele@ari.uni-heidelberg.de>
Date: Fri, 23 Jan 2015 15:51:43 +0100
Subject: [PATCH] [TAP] Update Javadoc of ServiceConnection

---
 src/tap/ServiceConnection.java | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/tap/ServiceConnection.java b/src/tap/ServiceConnection.java
index 37eddb2..0da1365 100644
--- a/src/tap/ServiceConnection.java
+++ b/src/tap/ServiceConnection.java
@@ -42,7 +42,7 @@ import adql.db.FunctionDef;
  * </p>
  * 
  * @author Gr&eacute;gory Mantelet (CDS;ARI)
- * @version 2.0 (12/2014)
+ * @version 2.0 (01/2015)
  */
 public interface ServiceConnection {
 
@@ -204,7 +204,8 @@ public interface ServiceConnection {
 	 * </ul>
 	 * 
 	 * <p><i><b>Important note:</b>
-	 * 	To save performances, it is strongly recommended to use ROWS limit rather than in bytes. Indeed, the rows limit can be taken
+	 * 	Currently, the default implementations of the library is only able to deal with output limits in ROWS.<br/>
+	 * 	Anyway, in order to save performances, it is strongly recommended to use ROWS limit rather than in bytes. Indeed, the rows limit can be taken
 	 * 	into account at the effective execution of the query (so before getting the result), on the contrary of the bytes limit which
 	 * 	will be applied on the query result.
 	 * </i></p>
@@ -228,7 +229,8 @@ public interface ServiceConnection {
 	 * </ul>
 	 * 
 	 * <p><i><b>Important note:</b>
-	 * 	To save performances, it is strongly recommended to use ROWS limit rather than in bytes. Indeed, the rows limit can be taken
+	 * 	Currently, the default implementations of the library is only able to deal with output limits in ROWS.<br/>
+	 * 	Anyway, in order to save performances, it is strongly recommended to use ROWS limit rather than in bytes. Indeed, the rows limit can be taken
 	 * 	into account at the effective execution of the query (so before getting the result), on the contrary of the bytes limit which
 	 * 	will be applied on the query result.
 	 * </i></p>
@@ -392,8 +394,6 @@ public interface ServiceConnection {
 	 * 
 	 * @return	NULL to allow ALL coordinate systems, an empty list to allow NO coordinate system,
 	 *        	or a list of coordinate system patterns otherwise.
-	 * 
-	 * @since 2.0
 	 */
 	public Collection<String> getCoordinateSystems();
 
-- 
GitLab