Add and option to use "SQL Server 2012" features/dialect and use OFFSET and FETCH for paging.

The new SQL Server 2012 paging feature will offer better performance and generated sql will be easier to understand.

http://www.mssqltips.com/sqlservertip/2696/comparing-performance-for-different-sql-server-paging-methods/

Possibility to choose UPPER Casing for URL Encoding's ie %2F, as many public API using OAuth use upper cased encoding for signing.

see http://oauth.net/core/1.0a/#signing_process

In WCF, I can create a udp endpoint discovery to allow client finding the service without knowing the endpoint addresses.

Is there a similar approach using restful servicestack so that the client could discover the end point addresses using some kind of discovery detection ?

Right now only request object is parsed for ApiMember attributes to generate documentation page. We've added support to parse all properties and show documentation for "subtypes".

Is it that much more work to add documentation to parse response object in similar manner? And show documentation for it as well?

Ideally it'd be in sections on the meta doc page.
Request
request types

Response
response types

I can take a stab at it, but might misdesign again.

Add a property to Remove the /Auth route, in favor of only /Authenticate instead.

Currently, I've added the following to hide /Auth routes.

                // This is a way to remove the /Auth route and leave /Authorize instead. We don't need 2

                ServiceRoutes = new Dictionary<Type, string[]> {{ typeof(AuthenticateService), new[] { "/" + localize(LocalizedStrings.Authenticate), "/" + localize(LocalizedStrings.Authenticate) + "/{provider}" }}},

Maybe there is a better way? Or is this bad?

At this time, StackExchange.Redis is the only .Net library I can find that supports SSL connections to Azure Redis. I imagine others will follow suit. It would be useful to have SSL connection available in ServiceStack as well. Thanks.

Just it! I would like to use the SSE feature with load balancing.

The MessagePack format seems pretty ideal for communication between a ServiceStack service and a Silverlight client. Unfortunately there is no PCL package for ServiceStack.MsgPack.

On top of that it would be useful to split the client and server parts into separate packages.

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

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.