Protection level of BeatPulseFilter + BeatPulseMiddleware

[stephenpope]

I am building an application (for sake of getting into pointless detail) I cant use the UseBeatPulse() Webhost extension.

I was hoping to be able register the IStartupFilter / BeatPulseFilter myself but this is private/internal.

So I thought I would register the middleware BeatPulseMiddleware myself but this is also private/internal.

Is there a reason for this level of security on these classes? I am keen to use BeatPulse but this has de-railed any progress I can make currently :)

[unaizorrilla]

Hi @stephenpope, this is not about "security", is about don't expose internal things. But, your are right, the BeatPulsePulseMiddleware should be public as asp.net usually does . In next version, probably tomorrow, I will make this change. Hope this help!

Thanks for fill this issue!!

Unai

[unaizorrilla]

Fixed on 70de175 BeatPulseMiddleware is public from version 1.7.1

[stephenpope]

Thanks for the quick fix :D

[unaizorrilla]

hope this help!