Opened 15 years ago
Closed 15 years ago
#5436 closed task (fixed)
Rename xmlrpc plugin to tracrpc
Reported by: | Thijs Triemstra | Owned by: | osimons |
---|---|---|---|
Priority: | normal | Component: | XmlRpcPlugin |
Severity: | normal | Keywords: | |
Cc: | Thijs Triemstra | Trac Release: | 0.11 |
Description
The XmlRpcPlugin recently received support for JSON, allowing you to use JSON for RPC calls to query Trac. This means it's not strictly a XML-RPC only plugin anymore. The actual package name of the plugin is tracrpc and this sounds like a much better name. I am planning on adding AMF support as well, using PyAMF, and that way this plugin can become a generic RPC plugin for Trac.
Attachments (0)
Change History (4)
comment:1 Changed 15 years ago by
Severity: | critical → normal |
---|
comment:3 Changed 15 years ago by
Priority: | high → normal |
---|
Replying to thijs:
Looks like this became the TracRpcProtocolsPlugin?
Actually adding various new protocols outside the default supported XML-RPC and JSON-RPC protocols, seems to be the intention of TracRpcProtocolsPlugin.
This ticket is all about renaming the XmlRpcPlugin to something with a less specific name now that XML-RPC is just one of potentially many supported protocols - typically the suggested TracRpcPlugin
or similar. It should stay open as I won't manage a transition to a new name now.
comment:4 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
[7916] completes the partial transition to new TracPRC naming as far as possible, but there is no real point in changing completely. I can't see myself aiming for further removal from origin, so closing as done.
Yes, as mentioned on #5437, a future version 1.1.0 will be further reworked to be fully protocol-agnostic (extension point), and that would correspond well with renaming it to just use simple forms of 'tracrpc' and 'rpc' naming.
I'd hesitate to call it a 'critical' issue as things do kind of work today... I'll leave the priority though as it is high on my list.