search

Breeze / breeze.js.labs

OFFICIAL Breeze.js Labs package of extensions and utilities for Breeze.js client apps.
MIT License
43 stars 44 forks source link

Nuget package for saveQueueing? #6

Closed markvp closed 10 years ago

markvp commented 10 years ago

Hi guys,

I noticed that you have Nuget packages for many of your labs outputs; but saveQueueing isn't available?

I'd be happy to assist with Nuget packaging if necessary but given you manage the others yourselves, is there any chance you could just include an additional Nuget package for saveQueueing?

Thanks,

Mark

wardbell commented 10 years ago

The reason it there isn't a nuget package for it is because I don't endorse it. I endure it. I have deeply mixed feelings about promoting it. I suppose I should get over them because it has been around long enough and been used widely enough. Let me give it a wee bit more thought :-)

markvp commented 10 years ago

@wardbell, is that saveQueueing that you don't endorse or nuget packaging?

If saveQueueing, what is your concern?

We have two items displayed on screen at once. If values do not exist for these items, our service creates default values and saves them. I allow these to run concurrently because they are entirely independent. The only reason to make one wait for the other (which I could do in theory) would be because of the technical limitation of the underlying provider (breeze). I suppose that, thinking about this, in my context there is little difference between using saveQueueing and just allowing concurrent requests since the failure of the first request should have minimal impact on the second request.

I'm curious about your thoughts though.

Mark

wardbell commented 10 years ago

Sorry for delayed response.

I just feel queasy about saveQueueing.

I have my beef with nuget too! But that's a story for another day.

It just doesn't feel right to start saving the same entity again while the initial save is in flight. I don't trust that all variations will work out ... especially if the server rejects one of the saves along the way. I'd prefer to design around the problem so everything is more deterministic.

As for your scenario ... if the the two items are truly independent, you don't need saveQueueing. Breeze only blocks if you try to save the save entity twice while it is already in flight.

So I'm probably going to hold off on making the nuget for this if you don't mind.

Btw, there's a fresh version up there that works with Angular (no Q.js) and Breeze v.1.4.14 or later.