|
From: Ryan J. M. <ry...@da...> - 2008-06-24 12:26:08
|
On Jun 23, 2008, at 7:48 PM, Bill Burke wrote: > > >> if these make sense, would it make sense to provide that in >> resteasy and have a way to differentiate the package with the others? > Here's a few ideas for innovation that I've come up with: > > * We already have a Client Proxy Framework. > * PathInfo rewriting (like URL rewriting, but only the path and only > with JAX-RS expressions) > * Client Framework support for CacheControl > * ServerSide CacheControl support. Annotate a JAX-RS method with > default CacheControl options. Cache the marshalled response on the > server to avoid reprocessing and re marshalling. > * Asynchronous HTTP (COMET) support. Ability to suspend within a > JAX-RS > request. > * Asynchrnous JAX-RS. Basically implement a Job Queue with asyncrnous > JAX-RS endpoints. (See RESTFul Web Services book). > * Combine ideas from Resteasy MOM (the JMS facade I wrote) with Asych > JAX-RS and JBoss Cache and basically create a lightweight, RESTful > ESB-like thingy. > * Provide Ruby, Python, and PHP versions of JAX-RS. (Not sure if this > is even possible :) ) (Groovy and Scala should just work). > In regards to Ruby, we should take a look RoR's ActiveResource: http://wiki.rubyonrails.org/rails/pages/ActiveResource They've been doing some cool stuff and there's some ideas in there we might want to consider ourselves. > > > Another big thing to differentiate ourselves is with exactly what > you're > doing. Provide examples on how to integrate with various > technologies. > In your case Spring + Hibernate + OAuth. I was thinking of writing > an > Adobe Flex application using JAX-RS as the backend. > I've already got the foundation for such an app that I just need to repackage. With that said, I'd like to propose that we create project for some examples. We'd have a subdirectory in the repo such that: resteasy-examples +- pom.xml +- example1 +- pom.xml +-example2 +- pom.xml Ideally, I'd like to have a suite of examples much like the Seam project has. If people are cool with this, I'll have this set up by the end of the week. > Another way to differentiate is to have a shitload of connectors. > Some > ideas I have are POI readers/writers (for MS docs). Agreed. I have a few that I started from the original RESTEasy that didn't get into SVN. They are: IIOImageProvider PDFProvider SVGProvider Some will take a bit more time that others. > Another way to is to have cool applications on top of Resteasy. i.e. > Resteasy MOM, maybe a automatic Hibernate RESTful interface. > Can you elaborate on the automatic part? > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Resteasy-developers mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-developers |