-
Notifications
You must be signed in to change notification settings - Fork 0
Release Notes
##Service Stack 1.79 Release Notes
- Enhanced REST functionality and access, now more succinct than ever
- Uploading of files to ServiceStack web services using HTTP POST multipart/form-data
- More robust error handling support handling C# exceptions over REST services
- For examples of on how to use the C# REST client API check out the tests in the new REST Files project:
New RestFiles project added to ServiceStack.Examples GitHub project:
Live demo available at: servicestack.net/RestFiles/
- Provides a complete remote file system management over a REST-ful api
- The complete REST-ful /files web service implementation is only 1 C# page class
- Includes a pure ajax client to provide a GitHub-like file browsing experience, written in only 1 static HTML page, using only jQuery
- C# integration test examples are also included showing how to access this REST-ful api over sync and async C# clients
Read the rest of the Rest Files README.md for a more detailed overview about the project.
- New users should download ServiceStack.Examples - v1.79
- Existing users can download just the ServiceStack.dlls - v1.79
.
##Service Stack 1.78 Release Notes
-
Added more tests and fixed bugs in ServiceStack's new CSV format and Request/Response filters
-
Added new information on the generated web service index, individual web service page now include:
- REST paths (if any are defined) thanks to @jakescott
- Included directions to consumers on how to override the HTTP Accept header and specify the format
- Now including any System.CompontentModel.Description meta information attributed on your Request DTO
- Preview the new documentation pages on ServiceStack Hello and Movies example web service pages.
-
Added tests to show how to implement Basic Authentication using the new RequestFilters
-
Changed the httpHandler paths in the Example projects and created a new Config class to store which supported mappings go with which web servers + middleware.
-
Provide a way to register new urls for different ServiceStack handler mappings used, e.g. to register IIS 6.0 urls:
SetConfig(new EndpointConfig { ServiceEndpointsMetadataConfig = ServiceEndpointsMetadataConfig.GetForIis6ServiceStackAshx() });
##Service Stack 1.77 Release Notes
This release was focused to opening up ServiceStack to better support adding more hooks and extension points where new formats can be added. The CSV format was also added to test these new extension APIs.
- Added support for the CSV format
- Enhanced the IContentTypeFilter API to add support for different serialization formats
- Added Request and Response filters so custom code can inspect and modify the incoming IHttpRequest or IHttpResponse.
- Added
Request.Itemsso you can share arbitrary data between your filters and web services. - Added
Request.Cookiesfor reading cookies (to avoid retrieving it from HttpRuntime.Current) - Removed the preceding UTF8 BOM character to ServiceStack's JSON and JSV Serializers.
- All features above are available on both ASP.NET and HttpListener hosts
Using the same tech that makes ServiceStack's JSV and JSON serializers so fast (i.e. no run-time reflection, static delegate caching, etc), should make it the fastest POCO CSV Serializer available for .NET.
The 'CSV' format is the first format added using the new extensions API, which only took the following lines of code:
//Register the 'text/csv' content-type and serializers (format is inferred from the last part of the content-type)
this.ContentTypeFilters.Register(ContentType.Csv,
CsvSerializer.SerializeToStream, CsvSerializer.DeserializeFromStream);
//Add a response filter to add a 'Content-Disposition' header so browsers treat it as a native .csv file
this.ResponseFilters.Add((req, res, dto) =>
{
if (req.ResponseContentType == ContentType.Csv)
{
res.AddHeader(HttpHeaders.ContentDisposition,
string.Format("attachment;filename={0}.csv", req.OperationName));
}
});
With only the code above, the 'CSV' format is now a first-class supported format which means all your existing web services can take advantage of the new format without any config or code changes. Just drop the latest ServiceStack.dlls (v1.77+) and you're good to go!
Note: there are some limitations on the CSV format and implementation which you can read about on the ServiceStack CSV Format page.
The Request filter takes a IHttpRequest, IHttpResponse and the Request DTO: List<Action<IHttpRequest, IHttpResponse, object>> RequestFilters { get; }
The Response filter takes a IHttpRequest, IHttpResponse and the Response DTO: List<Action<IHttpRequest, IHttpResponse, object>> ResponseFilters{ get; }
Note: both sets of filters are called before there any output is written to the response stream so you can happily use the filters to authorize and redirect the request. Calling IHttpResponse.Close() will close the response stream and stop any further processing of this request.
Feel free to discuss or find more about any of these features at the Service Stack Google Group
- Why ServiceStack?
- What is a message based web service?
- Advantages of message based web services
- Why remote services should use separate DTOs
- Getting Started
- Reference
- Clients
- Formats
- View Engines 4. Razor & Markdown Razor
- Hosts
- Security
- Advanced
- Configuration options
- Access HTTP specific features in services
- Logging
- Serialization/deserialization
- Request/response filters
- Filter attributes
- Concurrency Model
- Built-in caching options
- Built-in profiling
- Form Hijacking Prevention
- Auto-Mapping
- HTTP Utils
- Virtual File System
- Config API
- Physical Project Structure
- Modularizing Services
- MVC Integration
- Plugins 3. Request logger 4. Swagger API
- Tests
- Other Languages
- Use Cases
- Performance
- How To
- Future