On Mon, Mar 26, 2018 at 6:45 PM, Juan Manuel Garrido de Paz < juanm.garrido....@gmail.com> wrote:
> Hi Thiago, does it make sense to use tapestry just as a middleware between > a javascript client-side framework and the server? Just for implementing a > REST API that gathers the requests from the client and calls the server > methods that implement the use cases? > Hello! If you're not using Tapestry components at all, then yes, it may not make sense to use tapestry-core (i.e. the Web framework), but Tapestry-IoC would still be very useful for organizing your server-side code. On the other hand, even without Tapestry components, you could still use tapestry-core for its pipelines, specially HttpServletRequestFilter (for security, monitoring, etc) and Dispatcher. Also, using Tapestry pages for delivering non-HTML and non-JSON files (for example, delivering files stored in a database or a filesystem) and anything else which doesn't fit a typical REST endpoint. -- Thiago
