Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split IOutboxStorage into 2 interfaces #2659

Open
synhershko opened this issue Feb 20, 2015 · 10 comments
Open

Split IOutboxStorage into 2 interfaces #2659

synhershko opened this issue Feb 20, 2015 · 10 comments

Comments

@synhershko
Copy link
Contributor

In Particular/NServiceBus.RavenDB#43 (comment) we've stumbled upon a possible friction point with external storages, as one method (Store) requires a shared session (via session provider) and the rest create their own separate sessions.

This creates a friction point as the persister requires both a session provider and a DB connection (DocumentStore in RavenDB's case), and there are some edge cases where the 2 may point to different DBs.

To avoid this, @andreasohlund suggested we split IOutboxStorage into 2 - the deduplicator side of things (Store) into one and the rest into another.

@SzymonPobiega
Copy link
Member

👍 I notices the same when working with NHibernate one

@danielmarbach
Copy link
Contributor

Is this still on the radar?

@andreasohlund
Copy link
Member

Think it's a good change, not sure about how urgent it is though

On Mon, Apr 20, 2015 at 10:40 AM, Daniel Marbach [email protected]
wrote:

Is this still on the radar?


Reply to this email directly or view it on GitHub
#2659 (comment)
.

@SzymonPobiega
Copy link
Member

I like the change. It would even more important if we decide to go for explicit context sharing between handlers because that context would only need to access the store method.

@andreasohlund
Copy link
Member

I guess we would then pass a "context" to the Store to avoid needing DI.

I'm sold :)

On Mon, Apr 20, 2015 at 1:08 PM, Szymon Pobiega [email protected]
wrote:

I like the change. It would even more important if we decide to go for
explicit context sharing between handlers because that context would only
need to access the store method.


Reply to this email directly or view it on GitHub
#2659 (comment)
.

@danielmarbach
Copy link
Contributor

@DavidBoike should we close this one because it is tracked in feature dev?

@DavidBoike
Copy link
Member

How would that affect potential future release notes?

@danielmarbach
Copy link
Contributor

danielmarbach commented Jul 15, 2015 via email

@DavidBoike
Copy link
Member

This is not really in progress, I think it's here only because of how NSB repo was brought into Waffle. Where should this go?

@DavidBoike
Copy link
Member

Nevermind, I found its friends. All moved back to the Backlog, and I'll be removing my face as there is no current plan to do this soon.

@DavidBoike DavidBoike removed their assignment Sep 15, 2015
@andreasohlund andreasohlund modified the milestone: Future Oct 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants