[
https://issues.apache.org/jira/browse/GUACAMOLE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152405#comment-17152405
]
Mike Jumper commented on GUACAMOLE-1123:
----------------------------------------
Perhaps not so much standardize on a single _endpoint_ (the current endpoints
for global connection history, per-connection history, global user history,
etc. make RESTful sense), but standardize on a single representation
({{ActivityRecordSet}}) and means of exposing that representation (always
filterable, sortable, etc.)?
Either would eliminate a good amount of duplicate code, but I think
standardizing on {{ActivityRecordSet}} would be cleaner and more flexible.
> Standardize on filtered history query for user and connection management
> ------------------------------------------------------------------------
>
> Key: GUACAMOLE-1123
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1123
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-auth-jdbc
> Reporter: Nick Couchman
> Assignee: Nick Couchman
> Priority: Minor
>
> When querying connection history, there are several disparate endpoints that
> are used to gather that history. Instead of maintaining these various
> interfaces, we should standardize on a single connection history endpoint and
> update all of the relevant REST calls within the AngularJS application to
> reference those calls.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
