Skip to content

Because embedding a REST server in your application should be simple.

License

Notifications You must be signed in to change notification settings

ming86/Grapevine

 
 

Repository files navigation

The best solutions are the simplest to implement. Embedding a REST/HTTP server in your application should be simple. Consuming REST resources from inside your application should be simple. If what you've been using doesn't feel simple, try Grapevine. It doesn't get any simpler than this.

Introduction

Grapevine is a .NET class library focused on solving two problems:

  1. Easily embedding a REST/HTTP servers in your application
  2. Easily consume REST resources in your application

The focus is on simplicity, and Grapevine is intended for use in applications for which being a REST or HTTP client or server is not the primary function or purpose of the application.

Features

  • Grapevine can serve both static files and dynamic resources

  • Grapevine can both produce and consume REST services

  • Grapevine has minimal configuration requirements

  • Grapevine allows you to map specific methods to HTTP Method and URL patterns

  • Grapevine supports using regular expressions

  • Grapevine streamlines connecting and communicating with REST servers using simple patterns and placeholders

  • Grapevine can listen on multiple ports, and scope REST resources to those ports

Limitations

  • If an application needs to scale and/or balance load across multiple servers, it would likely benefit from the features offered by an enterprise service bus (ESB). While Grapevine would not likely be a good fit for an ESB, it can certainly facilitate communication with them.

  • Grapevine is not intended to be a drop-in replacement for Microsoft IIS or Apache HTTP Server. Nor is it a full-featured application server (like Tomcat) or framework (like Spring). Instead, Grapevine aims to be embedded in your application, where using one of those would be impossible, or just plain overkill.

  • Grapevine does not do any script parsing (PHP, Perl, Python, Ruby, etc.) by default - but feel free to fork this project and hack away! I'm pretty sure it could be done, I just haven't encountered a need for it (yet).

  • You will likely be required to open a port in your firewall for remote computers to be able to send requests to your application. Grapevine will not automatically do that for you. You might want to do that during the installation of your application.

Support

If you find you are having problems and need help check out our support options.

"Grapes In Dark Blue Cloud" Icon courtesy of aha-soft.

About

Because embedding a REST server in your application should be simple.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C# 100.0%