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

Service Host should deal with Azure/Windows envrionments #19

Open
mattridgway opened this issue Mar 11, 2015 · 2 comments
Open

Service Host should deal with Azure/Windows envrionments #19

mattridgway opened this issue Mar 11, 2015 · 2 comments
Milestone

Comments

@mattridgway
Copy link
Contributor

To make the code more implicit we should change the service host extension methods so that composition looks like the following:

//Thread falls through after it has run, service would stop
app.OnStart<Xsi.Projector>(projector => projector.Receive).ThenStop();
app.OnStop(projector => projector.Dispose);

//Thread is held after it has run, like listening for new event from hub
app.OnStart<Xsi.Projector>(projector => projector.Receive).ThenBlock();
app.OnStop(projector => projector.Dispose);

//everytime it finishes it loops around and starts again
app.OnStart<Xsi.Projector>(projector => projector.Receive).ThenLoop();
app.OnStop(projector => projector.Dispose);

@mattridgway mattridgway added this to the later milestone Mar 11, 2015
@smudge202
Copy link
Collaborator

This should be pretty easy to accomplish. Basically, by default we'd expose the CancellationToken, but the helpers can manage the token in order to provide the above extensions.

+1

@smudge202
Copy link
Collaborator

This needs to be moved to smudge202/compose-azurecloudservice

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

2 participants