Feature #814
HTTP/REST/JSON Web API
| Status: | New | Start: | 02/26/2013 | |
| Priority: | Normal | Due date: | ||
| Assigned to: |  Mirco Bauer |
% Done: | 0% |
|
| Category: | Engine | |||
| Target version: | 1.1 | |||
| Complexity: | High |
|||
| Votes: | 3 (View) |
Description
Smuxi needs to replace the .NET Remoting API with a Web API as .NET Remoting is deprecated , is not supported on mobile .NET platforms (like MonoDroid and MonoTouch) and limits frontends to a .NET based or enabled programming language. For this reason a modern and cross-language web API is needed that makes use of current web standards like HTTP, REST and JSON.
ServiceStack and SignalR are candidates to reach this goal.
A playground which interfaces this web API needs to provide can found here: https://live.gnome.org/Smuxi/Protocol/Zero
Related issues
| related to Smuxi - Bug #589 | remoting error since updating smuxi-server to Mono 2.10.1 | Closed | 04/20/2011 | ||
| blocks Smuxi - Task #829 | let the engine handle autocomplete | New | 04/08/2013 | ||
| blocks Smuxi - Feature #820 | DCC/XDCC | New | 03/12/2013 | ||
| blocks Smuxi - Feature #816 | Customize Xmpp's ProtocolChatView | New | 02/26/2013 | ||
| blocks Smuxi - Feature #793 | Android frontend | New | 12/30/2012 | ||
| blocks Smuxi - Feature #815 | Proper Contactlist for xmpp | New | 02/26/2013 |
History
Updated by Mirco Bauer 3429 days ago
For push notifications WebSockets are also a candidate.
C# WebSockets client+server implementation licensed under MIT:
https://github.com/sta/websocket-sharp
Updated by Mirco Bauer 3413 days ago
The issue of no message IDs should be addressed before this. This is critical for querying the engine for older messages in a reliable way:
https://github.com/meebey/smuxi/commits/experiments/message_buffer_timestamps