Using servicestack client in mobile development with Xamarin gives so much benefits and caching dramatically improves performance and user experience.
It would be nice to have same caching support for all clients (.NET, JAVA, ..)

"OpenID Connect (OIDC) is an authentication layer on top of OAuth 2.0, an authorization framework." The benefit to developers and consumers is a more simplified way to add a new Auth provider which would provide some standard user info.
http://openid.net/connect/

I've started working with request batching, which is a really nice feature. Everything works, but there two improvements I'd like to see.

Firstly, for IReturnVoid requests there is SendAllOneWay, but there is no async version of that method.

Secondly, I'd like to be able to specify a http Verb with the SendAll methods. The implementation should select the correct method in the service, both when calling a single request method multiple times, but also for the batched method. Right now the batched service methods always need to be Any(), it would be nice to be able to have Delete(OrderID[] orders).

Much like you have created a RedisSentinel object ... I have a need for a RedisCluster object that supports the new feature which is coming in v3.0. Thanks.

Swagger now support oAuth login page to create a access_token to apply to a oAuth protected API: http://developers-blog.helloreverb.com/enabling-oauth-with-swagger/

Please could you add a similar capability to ServiceSatck.SwaggerFeature that enables SS developers to add a similar capability to their own APIS that are protected by oAuth.

Support to automatically update a db schema based on changes such as: adding/renaming and possibly removing a property or class.

e.g:

db.Save(poco, references: true, deleteMissing: true);

from: https://forums.servicestack.net/t/ormlite-graph-update/1395

Being able to bulk insert/copy would be cool.

Adding support in so I could just take a list and

Db.BulkCopy(listOfObjects);

would be pretty sweet.

SqlServer has the bulkCopy object, postgres has the copy command, sqlite has import (although no idea how well that works) , and mysql...well...who cares (i don't know what they have)

Having a single interface for bulk copying objects into different databases I think would be a nice feature for ormlite. (not sure how feasible)

Support Azure DocumentDB as an available caching provider for Azure hosts.

Currently redis client is not async - this is wasting valuable resources on the server side. As far as I understand async support is currently only there for service clients and not redis

Currently to send in an integer array as a parameter, I have to use format.

var ids = "ARRAY[1,2,3]";
var sql = "SELECT 1 = ANY[{0}]".Fmt(ids);
Db.Query<Model>(sql);

I would rather use syntax like this:
var ids = new int[] {1, 2, 3};
var sql = "SELECT 1 = ANY(@ids)";
Db.Query<Model>(sql, new { ids });

Add a Trace method to Log/ILog in do verbose logging

While being able to offload to statsd/graphite/raygun/... is great, a "state of the nation" dashboard would be really handy.

This could show requests/sec, wait times, "slow" requests, auth failures, live access map, recent exceptions, known issues (e.g. can't connect to redisX/mssqlY)

Create [self-hosted] apphost where all request messages are automatically registered to the MQ message service,
so that all services can be accessed via MQ without the need to register every request type manually with something like "mqServer.RegisterHandler<Hello>(...)" .

It would be nice if the order of operations of the mq message handling could be further aligned to the http variant.

Currently Oracle is not a supported OrmLite provider that's listed on:
http://servicestack.net/download

Vote for this feature request if you would like to see the OrmLite Oracle provider officially supported.

support localization in messages for validations or any other messages sent to the client

Building upon swagger feature, (but possibly re-engineering)

Support to include:
- complex (nested) DTO's and array
- markdown documentation (for detailed description)
- role/access based display (so only authorised endpoints are displayed)
- rebranding support
- ability to install nuget package without /docs folder (so as to get annotations, but not html in a model lib)