From 23d3e5081272a8ca53b092e79d1e716641ad8f30 Mon Sep 17 00:00:00 2001 From: Kegsay Date: Tue, 20 Jan 2015 17:48:43 +0000 Subject: [PATCH] Add use case justification for regex --- drafts/application_services.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drafts/application_services.rst b/drafts/application_services.rst index 2c73107f..c654c010 100644 --- a/drafts/application_services.rst +++ b/drafts/application_services.rst @@ -85,7 +85,8 @@ In the registration process, the AS provides: * Details of the namespaces of users and rooms the AS is acting on behalf of and "subscribing to" * Namespaces are defined as a list of regexps against which to match room aliases, - room IDs, and user IDs. + room IDs, and user IDs. Regexps give the flexibility to say, sub-domain MSISDN + ranges per AS, whereas a blunt prefix string does not. * There is overlap between selecting events via the csv2 Filter API and subscribing to events here - perhaps subscription involves passing a filter token into the registration API.