On Tue, 02 Aug 2016 14:41:24 -0300, Juan M Garrido de Paz
<juanm.garrido....@gmail.com> wrote:
How is the approach of use tapestry just to offer web services to the
frontend? In this case tapestry just serves json objects? Then you dont
need tapestry components and other features for anything , do you? I dont
see the point of using tapestry in this case.
Live class reloading makes your development way faster.
And using tapestry pages instead of web services? Pages here are for
nothing but to hold the event listener method that do the job by calling
the model service, arent they?
In this case, yes.
I dont see why to use tapestry as the web framework in this cases, as you
just use it as a middleware to call model services. You dont use pages,
components, zones, etc.
You lose using the Tapestry pipelines (specially RequestFilter) for access
control, profiling, logging, etc.
Anyway what do you think is better, using tapestry generating the
required front end code? Or using tapestry just to offer the services to
the front
end ? (either by web services or by page listeners).
Which approach do you prefer?
I believe the answer is very dependent on the actual scenario you have to
implement, so I won't give any broad answers.
I'm just saying that REST services can be done. I'm not saying it's the
best solution.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
