Re: the meaning of stateless

Thank you for your response.

The function that we are exposing is a reimbursement calculation that
has many different fields (> 200) that could alter the outcome.  Some of
the fields are basic flags and others are lists of items that could be
empty or up to as many as 100.  There isn't really any hierarchy to the
data or any value to expose them as resources individually.  Providing
the data in a POST would work but then the concern is we need to store
the output of the formula which also contains a good amount of fields on
the server in order to respond to the future GET.  We are eventually
going to feed this service into a larger application and would like to
be able to scale as we get large amounts of data fed through.  If the
result data is stored in memory, we would lose the ability to scale out,
and in essence make the system not "stateless".


--- In [email protected], Jan Algermissen  wrote:
>
> And if you really have to:
>
> On 22.04.2013, at 20:56, "scott vernon" vern33nova@... wrote:
>
> > so where would we store the intermediate data
>
> Build up the state on the client. Why does the intermediate state need
to be on the server in the first place? Why not just POST the large
'query'?
>
> Jan
>