# Sinatra, and web enabling existing .NET codebases

**URL:** <https://www.ruby-forum.com/t/sinatra-and-web-enabling-existing-net-codebases/171907>\
**Category:** IronRuby\
**Created:** [July 11, 2009, 8:03am UTC](https://www.ruby-forum.com/t/sinatra-and-web-enabling-existing-net-codebases/171907 "2009-07-11T08:03:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dotty](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/e56c9b/32.png) [@dotty](https://www.ruby-forum.com/u/dotty)\
**Post date:** [July 11, 2009, 8:03am UTC](https://www.ruby-forum.com/t/sinatra-and-web-enabling-existing-net-codebases/171907/1 "2009-07-11T08:03:29Z")

</div>

Aaron Quint gave a very interesting talk at GoGaRuCo:

[http://pivotallabs.com/gogaruco/talks/51-sinatra-the-framework-within](http://pivotallabs.com/gogaruco/talks/51-sinatra-the-framework-within)

About using sinatra to quickly and easily REST-enable libraries.  
I think this might be a very good fit where we’d like to web/REST enable  
our existing .NET codebase assets.

It looks like RESTClient is not quite ready to run from IronRuby (at  
least from my tests), but personally, I think this looks quite  
compelling as a IronRuby use case.

There are other alternatives for giving a REST interface to our .NET  
libs - REST service through WCF, or OpenRasta:  
[http://trac.caffeine-it.com/openrasta](http://trac.caffeine-it.com/openrasta)

But I think Sinatra/RESTClient may be faster/easier/less configuration  
than the more statically-oriented existing solutions.

Thoughts? Anyone already working on something like this? and if so,  
could you provide any insight into the best way to expose library  
functionality in this fashion?