[commits] [Wiki] changed: Project/H6TODO
Michael Slusarz
slusarz at horde.org
Tue Apr 1 09:02:46 UTC 2014
slusarz Tue, 01 Apr 2014 09:02:46 +0000
Modified page: http://wiki.horde.org/Project/H6TODO
New Revision: 4
Change log: API calls discussion
@@ -21,6 +21,8 @@
* Websockets version of AJAX endpoint
* Log improvements
* Ability to queue log entries (configurable), for logging after request.
* Also... right now, we need to fully process log entry before we
know if we are going to accept, since log level checking happens at
the lowest levels of logging chain. Need to move this up in chain so
that we can exit out of log code earlier if we know that we don't want
to process.
-
-
+* Application API access
+ * Current status is apparently that complex objects are not allowed
as return from API calls due to possibility that they may be returned
via RPC. But we have a bunch of code that does do this, and the
takeaway is that inter-application sharing is much much more important
than remote calls
+ * One solution: Have these calls return an object that will allow
to gracefully degrade if advanced object support is not available
+ * Or else figure out way to consistently determine how to
document calls not intended for remote access. I see absolutely
nothing wrong with allowing access to inter-application calls via
native PHP interface without allowing remote call. (Logistically,
this could be done by defining yet another API for applications. But
practically, this is better done within the existing framework to
minimize complexity).
More information about the commits
mailing list