Add a MQ Server for Azure Service Bus that implements ServiceStack's Messaging API: https://github.com/ServiceStack/ServiceStack/wiki/Messaging

Support http compression on clients (Xamarin/sl5) with Microsoft Compression BCL library

Add the ability to specify message-level encryption on all client/server requests. Allow custom selection of encryption techniques (RSA, AES, etc.) for each direction, and the initialization vectors. Server-side I can see doing this via plug-ins and / or attributes.

Create a subset of client libraries that handle encryption, perhaps using function pointers to encrypt / decrypt.

Its been suggested previously by Demois on different forums.

http://stackoverflow.com/questions/16098839/encrypting-messages-over-servicestack

http://www.linkedin.com/groups/Service-Stack-versus-ASP-NET-1779887.S.107976247

An AsyncCredentialsAuthProvider would allow us to authenticate users asynchronously (query a database, calculate hashes, etc). Right now when extending the CredentialsAuthProvider, we are limited to do everything synchronously in the TryAuthenticate method which can lead to thread starvation.

Add a MQ Server for Amazon SQS that implements ServiceStack's Messaging API: https://github.com/ServiceStack/ServiceStack/wiki/Messaging

I'd like to see an alternative to WCF Duplex Communications.

This is somewhat related to http://servicestack.uservoice.com/forums/176786-feature-requests/suggestions/4458942-add-fast-tcp-endpoint (Add fast TCP endpoint), as the duplex comms should use the same connection.

We use this for "playing nice" with firewalls (make connection out, poll in on same connection).

The Save method will populate the inserted PK value if the PK is an integer with [AutoIncrement].

It would be useful to also have this method use the database's internal GUID generator (which creates sequential GUIDs) and thus populate back into the object a GUID generated in the db.

By default, database's will create a clustered index on the PK field, if the GUIDs are not sequential and the column has a clustered index on it, then performance will suffer.

PostFileWithRequest works great, but user experience isn't great when this method is used to post large files (20+MB or even smaller files over a slow connection) to the server because there's no callback for progress notification.

Additionally, this method isn't async in SL5 builds, but we can work around this. We can't work around missing progress callback though.

Looking at the implementation of this method, this should be fairly easy to do. I will most likely submit a pull request with the implementation over the weekend.

We're an all MSFT shop, not much opportunity to use Memcache or Redis. A SQL Server Cache Client would be very useful.

Change how OrmLite stores complex type properties so they can be stored in formats other than JSV like JSON.

Xamarin support IOS/Android/Windows Store/Windows Phone. A universal Service Stack client written using PCL would simplify code reuse. The code could be packaged up into a Xamarin Component Store download if necessary. Or be used in conjunction with MvvmCross for use in MVVM style coding and/or unit testing.

This would be very nice to have, in both the ServiceStack client AND server. The server part would be preferred, obviously :)

Add better support for Joins and fetching related records.

Add more MQ Adapters, e.g: Rabbit MQ, Amazon SQS, Azure Service Bus, ZeroMQ/nanomsg.

https://plus.google.com/u/0/103098793536210174759/posts/FdZJrFiAWi2

Research optimal deployment strategies for hosting ServiceStack on Linux (e.g. nginx FastCGI/ nginx + reverse proxy / self-hosting inside linux daemon) with the best performance, that best supports CI deployment with no downtime, auto restart/recovery when Mono process dies.

Change ServiceStack to be based on IHttpAsyncHandler so services have the option to be non-blocking by returning a Task<T>.