I am confused. 100 objects can as easily be created in one transaction
as in a hundred transactions, can they not?
Are you (John) trying to say that REST has some impact on a client's
ability to enclose 100 objects in one transaction? This may be true: I
have never tried big transactions over
I mistakenly wrote:
I am confused. 100 objects can as easily be created in one transaction
as in a hundred transactions, can they not?
...
Please ignore that message, which both represented my misunderstanding
of the HTTP PUT method, and did not take into account the full context
of the
Here's where I believe the issue lies: 1. Adding approximately 100 or more
objects to a collection backed by a relational database, in an interactive
system. I believe the time for the transaction(s) took too long. I am not
sure if the REST service supported by the database used a single
John Carlson wrote:
Here's where I believe the issue lies: 1. Adding approximately 100 or
more objects to a collection backed by a relational database, in an
interactive system. I believe the time for the transaction(s) took
too long. I am not sure if the REST service supported by the
Not really obfuscating. Just trying to explain that 1 transaction is going
to work faster than 100 transactions. If you agree with that, I have no
problem. If not, you might also believe that putc performs as fast as
puts, which is wrong.
On Feb 14, 2013 4:59 PM, Miles Fidelman
