Hi Jan,
algermissen1971 wrote:
>
> Leo,
>
> make your process a resource that changes state over time.
>
I'd love to do so. To some extent, our current RESTful API follows this
idea. We use the patterns like:
POST /service/startProcess -> would return the process id of newly started
process
GET /service/process_id/state_resource_path
DELETE /service/process_id
But as I mentioned, this process has a LOT OF state. Replicating its state
between cluster nodes is very difficult and inefficient for different
reasons. Therefore, only the cluster node owning the process can process
requests related to it. And I do not see yet how your proposal helps in this
regard. Or may be I misunderstand what you say?
-Leo
--
View this message in context: http://jersey.576304.n2.nabble.com/Providing-a-stateful-JAX-RS-service-in-a-cluster-tp6063881p6063914.html
Sent from the Jersey mailing list archive at Nabble.com.