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.

Sign up for GitHub

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

Jump to bottom

Refactor Operations: Requester, Responder & Subscriber #64

Closed
pardahlman opened this issue Mar 1, 2016 · 0 comments
Closed

Refactor Operations: Requester, Responder & Subscriber #64

pardahlman opened this issue Mar 1, 2016 · 0 comments

Comments

@pardahlman
Copy link
Owner

No description provided.

@pardahlman pardahlman changed the title Refactor Operations: Requester Refactor Operations: Requester, Responder & Subscriber Mar 5, 2016
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64): Change response cast strategy
bfa88b3 
Instead of having a dictionary with value as object we have Tcs<object> that
is casted upon task completion.
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64): Prefetch for Requester is allways 1
1a8869d 
No point in even trying to get more than one response
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64) Use header to determen message type
6fe8897 
Rather than relying on generic argument. This is because I want to move from
having one consumer per type, but rather have consumers that can handle
messages comming in.
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64): Update error handler signature
b7f54ee 
Since it will get an TaskCompletionSource<object>, no matter the response type.
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64): First stab at DynamicChannelFactory
9a51b0b
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64): Add Scaling abilities to DynamicChannelFactory
b5d786a
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64): Use topology specific channel
720dfbb 
That exists for two seconds. It should be enough for any application to
create most of its queues and exchanges.
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64): Migrate Requester to new infra
3b6ac11 
That is, using the TopologyProvider for topology stuff and using the
channel factory for retrieving channel.
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64) First stab at new responder
8e3db83
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64): Allow ChannelFactory to have 0 channels
5230e25
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64) Add 'IsInitialized' method
4c0e1ee 
That can be used to keep the number of tasks created down.
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64) Remove locks from Requester
d335b77
pardahlman pushed a commit that referenced this issue Mar 5, 2016
(#64): Migrated Subscriber to new infra
6a5635d 
And by doing so, no one uses the operation base anymore, so it's gone baby,
gone.
@pardahlman pardahlman mentioned this issue Mar 5, 2016
Closed
pardahlman pushed a commit that referenced this issue Mar 6, 2016
(#64) Register correct channel factory for Autofac
5aa6f91
pardahlman pushed a commit that referenced this issue Mar 6, 2016
(#64) Register correct channel factory for Autofac
8206856
pardahlman pushed a commit that referenced this issue Mar 6, 2016
(#64) Add unit tests for ChannelFactory
494e995
pardahlman pushed a commit that referenced this issue Mar 6, 2016
(#64) Update documentation
3e7626f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pardahlman