If the MyGet builds are marked as pre-release then it will be easy to move between MyGet builds for the same version number and also easier to upgrade to the NuGet stable build when it is released.

I deploy to Azure Web Sites which does the nuget package restore and full solution build for me. In order to move between MyGet builds or move to the stable NuGet build, I have to log in and manually delete the package cache on every site. If the MyGet builds had their own unque version number, upgrades would be easier.

Refer to http://www.codeproject.com/Articles/873615/Announcing-Microsoft-IO-RecycableMemoryStream

Quote:
Microsoft.IO.RecyclableMemoryStream is a MemoryStream replacement that offers superior behavior for performance-critical systems. In particular it is optimized to do the following:

Eliminate Large Object Heap allocations by using pooled buffers
Avoid memory leaks by having a bounded pool size
Avoid memory fragmentation
Provide excellent debuggability
Provide metrics for performance tracking

Akin to the EF "Include" method, enhance OrmLite's LoadSelect method to take an optional string array of references to load. For performance reasons, I don't always want to load all references to an object, particularly if its a central object like Account or User. As a coding efficiency measure, it'd be great to pass in a list of only the reference objects or properties that are relevant to the code snippet.

Currently if we want to customize the Auth DTO Response in Credential Auth Provider, we must to rewrite the Auth Feature,the Authentication Service and the Credential Provider.
It would be useful to be able to set a custom auth DTO Response.

At this time there isn't a simple solution.
I found this post on stackoverflow that explains the problem in details:

http://stackoverflow.com/questions/16280319/return-a-custom-auth-response-object-from-servicestack-authentication

4.0.34 version of ormlite gives null for an async call
for example

// user1 is not null in this case
var user1 = db.Single(db.From<Users>().Where(x => x.UserPartyId == userPartyId).Select());

// user2 is null in this case
var user2 = await db.SingleAsync(db.From<Users>().Where(x => x.UserPartyId == userPartyId).Select());

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

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.