Feature Requests
Feature, docs and use-case samples requests for ServiceStack. If you can, focus on the end-user benefit / use-case, rather than the technical details so we can focus on the end-goal and free us to work on how best to achieve it. Features can also include supporting content, e.g. a starter project on how to use ServiceStack with another product (e.g. SS + SharePoint).
33 results found
-
OWIN compatible ServiceStack
With the OWIN specification being final, it seems like support is bound to happen sooner rather than later.
I believe some effort was made a couple of year https://github.com/ServiceStack/ServiceStack.Owin).
163 votesWhilst this feature requested OWIN support, it really wanted better integration with the external ecosystem outside of ASP.NET Handlers.
This is now resolved with .NET Core which has become the future Web Platform for .NET which as part of its design supports the integrations that OWIN was created to enable.
We’re happy to announce that ServiceStack now supports running on .NET Core where it now can happily co-exist with external frameworks, e.g. you can host ServiceStack + MVC together in the same default route space without being forced to mount ServiceStack at a custom `/api` route.
For more details on ServiceStack’s support and integration with .NET Core please checkout the full release notes: http://docs.servicestack.net/releases/v4.5.2.html
As this feature request was quite contentious I want to leave my closing thoughts on our hesitance to support OWIN:
With .NET Core it’s clear OWIN was the…
-
Add fast TCP endpoint
Add the most efficient remote endpoint for consuming ServiceStack services.
Ideas: use https://github.com/nanomsg/nanomsg (by author and successor to ZeroMQ in C).
Advantages: Abstracts IPC/TPC/InMemory for picking the most efficient transport. Can easily interoperate with other NanoMsg clients on other platforms. C is nice to embed than C++.
Disadvantages: Still in Alpha, unclear when it will be stable/safe to use. Still native, requires effort to use 32/64 bit architectures and cross-platform on Mono.Alternative: Build endpoint on raw TCP sockets in C# using something like Redis wire protocol for efficient transfer of message payloads. Could imitate operation on redis-server for interoperability…
105 votesgRPC offers a number of efficient communication channels over a persistent multi-plexed HTTP/2 connection using compact/efficient protocol buffers which would superseed most of the value a custom TCP channel would offer now that ServiceStack gRPC has been released:
https://docs.servicestack.net/grpcC# / F# / VB.NET Apps can also take advantage of our smart generic service clients to offer the simplest and richest development UX:
https://docs.servicestack.net/grpc-generic -
Add Integration with node.js
Improve integration with ServiceStack + node.js and add examples showing how to use ServiceStack as an efficient API back-end for a node.js-powered web application (as an alternative to MVC + ServiceStack).
Node Proxy example already at:
https://github.com/ServiceStack/ServiceStack.UseCases/tree/master/NodeStackProxy
If it's more efficient and gets Linux/Mono support ServiceStack could integrate with: https://github.com/tjanczuk/edge20 votesWe believe the best solution is to instead integrate with Webpack/parcel instead of proxying directly with a node.exe process.
Most of the SPA templates have great integration with Webpack and JS CLI tools:
http://docs.servicestack.net/releases/v5.2#net-core-templates -
Create Xamarin Components
Create ServiceStack components for the Xamarin Component store.
16 votesDeciding against creating separate Xamarin components at this time – NuGet packages are more re-usable and easier to manage.
You can add the NuGet Package Manager to Xamarin Studio to make it easier to install NuGet packages, see:
http://barambani.wordpress.com/2013/10/07/add-nuget-package-manager-and-servicestack-to-xamarin-studio-projects-2/Whilst the PCL ServiceStack clients that support iOS and Android are being maintained on: https://github.com/ServiceStack/Hello
-
Enable ServiceStack Services in UWP
Provide a package that allows hosting ServiceStack services (specifically web services and web sockets) in a UWP environment. The primary use-case for this is to allow ServiceStack services to run on an IoT device using UWP IoT Core.
13 votesNot possible to run ServiceStack Server in AOT environments. Only our Service Clients support UWP .NET Native AOT
http://docs.servicestack.net/releases/v5.2#support-for-uwp-net-native
-
9 votes
WP is dead and all ServiceStack libraries support .NET Standard 2.0 which is available for most active .NET platforms.
-
YAML
Please add support to YAML format.
Tags: ServiceStack.Text YAML serialization format
9 votesThere’s no plans for implementing and maintaining our own YAML serializer. Please refer to the docs for how you can register your own Custom Media Types like YAML:
https://docs.servicestack.net/serialization-deserialization#custom-media-types
-
Implement ideas and techniques from Jil for Json speed
Jil currently holds the crown for the fastet .NET Json serializer. There are some incredible tips/tricks/techniques that Kevin uses to achieve these speeds. Maybe it's possible to backport some of these into Servicestack.Text to increase serialization speed?
Latest benchmarks:
http://t.co/oQzvtR9FmT7 votesThis is not an actionable feature request and JIL uses an architecturally incompatible approach. But in the latest v5.2 release ServiceStack.Text internals has been rewritten to use .NET’s new Span memory types and has exhausted available perf wins for now.
http://docs.servicestack.net/releases/v5.2#spanified-servicestack -
Add ServiceStack + Dart + WebComponents / Polymer.js example
Add a starter template to make use of the next generation web framework by Google with Dart + WebComponents/Polymer.js https://www.dartlang.org/polymer-dart/
7 votesWe don’t see Dart + Web Components having a strong future, our efforts will be focused around React and AngularJS going forward.
-
ormlite - pre/post full events (pre: insert/update, post:insert/update)
Even though this is a lite/micro orm, these events are fundamentals and making the database fully auditable (by infrastructure).
I have never used an ORM without using all of these events.
Today only the pre-events are available.
There is a possibility to run code after and before you execute .save(), still.this is very pitfully...
Also, the events are static. it is a nightmare to get external context to inside the event. such as current logedin user...
6 votesThis comment contains misguided assumptions with how ORM’s work which require Singleton access to Request Contexts in order to access per-request context data like authenticated user info, explained in more detail with recommended solutions in this follow up thread:
https://forums.servicestack.net/t/ormlite-createdby-lastupdatedby/8288
-
Continue supporting .NET 4.0 projects
Microsoft has ended support for .NET 4, 4.5 and 4.5.1 on January 12th:
https://blogs.msdn.microsoft.com/dotnet/2015/12/09/support-ending-for-the-net-framework-4-4-5-and-4-5-1/We've started seeing some of our 3rd Party NuGet dependencies stop providing .NET 4.0 builds which is forcing us to reference old packages and prevents us from being able to access newer features.
As a result we plan to follow .NET recommendation and stop providing .NET 4.0 builds for all releases after August 1st, 2016.
If you absolutely need .NET 4.0 builds beyond this date please leave a comment on this request describing your use-case as well as the expected date before you will be able…
5 votesv4.0.62 was the last release supporting .NET 4.0: https://github.com/ServiceStack/ServiceStack/blob/master/docs/2016/v4.0.62.md#last-release-supporting-net-40
-
Refactor IRedisSubscription interface to be more intuitive
https://github.com/ServiceStack/ServiceStack.Redis/wiki/RedisPubSub gives a good example of how to use pub sub pattern. However, from the documentation that is provided with the API, I don't think there's a way to infer that in the property Action<string, string> OnMessage { get; set; } the first param is the channel,
and the second one is the msg. Other functions are pretty self explanatory, but for this one, I don't feel like I should have to thumb through a bunch of examples to have to figure out how to use it.
A more self explanatory pattern would be to have an actual event OnMessage…3 votesThe OnMessage is documented on both the wiki and the home page:
https://github.com/ServiceStack/ServiceStack.Redis#usageIf the API isn’t self-explanatory checkout the docs to see if there’s an example, otherwise feel free to ask a question on our Forums or StackOverflow.
I’ve added API docs in this commit https://github.com/ServiceStack/ServiceStack.Redis/commit/cc5f4ba416d5c904a9b483adf92a504c2e9e9dd9
But we wont be making any breaking changes to existing APIs.
-
Rate ServiceStack Customer Support Agents
I think having a rating on the developers who respond would help the company allocate resources more appropriately. Basically a 5 star rating system if you want to rate your interaction with their people, with the ability to make a comment about the quality of the service your received.
3 votesThis site is for feature requests you would like implemented in ServiceStack’s Software.
For completeness, I understand you’re frustrated and requesting this in response to your feature request being declined:
and my response to your comments on:
-
Support multiple API (service contracts) on the same AppHost
I would love to see that the AppHost supports multiple "API:s", or service contract, hosted on the same AppHost (and thus the same port), or several differnt AppHosts but using the same port...
I am using the sefl-hosted solution and I dont have a separate web server to do some mod-rewrites, reverse proxies and such (which is messy anyways).
The reason:
I have several "webservices", Ws1, Ws2 etc, and they often have some identical DTOs/methods (such as Login etc). I want to use only one IP:port that then makes these different webservices available under a prefixed path.So, for example,…
3 votesBeing able to invoke a Service by sending an encapsulated Request DTO which can only be realized by a single implementation is fundamental to ServiceStack.
-
Select and copy key values
When displaying a hash, it's impossible to select field or value to copy them
3 votesHave no idea what this feature request is about, please include all details and context so it’s absolutely clear what is being requested and the use-case it’s meant for.
-
Allow API documentation with comments
This may be related to this:
https://servicestack.uservoice.com/forums/176786-feature-requests/suggestions/4459106-api-explorer-meta-data-enhancementsWe have a lot of documentation to fill in, and while the Attributes are great for fine-grained details (if you need them), they are cumbersome with longer descriptions. It would be nice if I could just /// my classes / properties and ServiceStack would fill that in for the Notes (or maybe it's summary?). Maybe a swagger plugin option of ScanCommentsForNotes?
3 votesThe libraries don’t have access to comments which aren’t embedded in the .dll. You can use the `[Description()]` or Description property in `[Api*]` attributes to emit comments in DTOs.
-
AutoQuery additions/flexibility
It would be useful to have AutoQueries that could do
1. custom joins (currently, you have to write a service 'override')
2. generic, dynamic, or object as a return type!Potentially makes writing dozens of reports easy to maintain (for our department) because they are maintained from their source objects instead of having a DTO for each one, considering that regular joins already work that way where they do not require a custom return type to return!
3 votesCustom joins can’t be declared in a class definition, you would need to use a Custom AutoQuery implementation.
AutoQuery Services require populating a Typed Response DTO which is what’s needed to indicate which columns to return. Unknown return types can’t be documented in metadata services and can’t be consumed in any supported language which requires deserializing into a known type.
-
Enable FluentAPI to add dynamically response type
It's possible to add an overload in Fluent API to register also the response type together with the routing path?
For example: Routes.Add(requestType,restPath,verbs,responseType).
This can be useful when you can't use the IReturn Interface on DTO objects (for example inside UniversalApp PCL).
3 votesThis defeats the primary purpose of the `IReturn` marker for enabling a terse strong-typed generic API on Service Clients which is only possible if the generic type information is statically defined.
You can use one of the other fallback options for specifying the ResponseType:
https://github.com/ServiceStack/ServiceStack/wiki/Metadata-page#matching-requests-with-their-response-dtos -
Allow customization of authentication route verbs
It is currently possible to override the default authentication routes, but only the path can be set. It would be useful to be able to override the allowed verbs. I'd like to be able to prevent GET /auth/credentials, by limiting the endpoint to POSTs only. I've not been able to find any other ways of doing this.
3 votesCan use existing API’s.
-
OrmLite: Add support for CompositeKey attribute
My suggestion is to Add support for CompositeKey attribute for OrmLite, see
https://forums.servicestack.net/t/compositekeyattribute-does-not-create-any-composite-key-on-the-table/Thank you.
3 votesanswered in forums
- Don't see your idea?