Now with this, is there a better way

CodePudding user response:

Your id very well, the problem of the ans you also very well

https://bbs.csdn.net/topics/397089948

To tell the truth, you are a very diligent programmer, worthy of praise and praise, but I think you should it is time to bring you clear out the influence of blog garden, because the blog garden that is "practice the preliminary work, waste legs first, and then use my turn, turn your health such as fly, sharp as a ke zhen4 wu, handsome than the period of yanqing" -- -- -- -- -- -- -- -- -- -- -- -- it's a pity that is a lame man

Maybe this sentence above a lot of people don't want to listen to, don't want to see, because they don't want to admit that already limping, but we say, the front is lame lame, later don't since the waste as far as possible the "legs"

Stick to see you before you stick to everything, before we say don't need, because operations can be very good deal with the matter, you do your thing, don't need you to go to universal, because if you fail your legs, turn to universal, blog garden brother tell you again -- -- -- -- -- -- nullify your legs, not necessarily success -- -- -- -- -- -- -- -- -- -- -- -- we use Ocelot gateway, and then a bunch of people to chat and it will be called Ocelot (of course this is still a waste legs, still take dig eyes, behind the us talking)

Come to see you on the discount problem, in fact is still the same problem, why do you want to universal, we do not universal, we are not god, admit that he is not god, it would be nice, admitted that he is not god, of course, that means we are people, people want to have my legs, don't cut, you to do at ordinary times, how do you normally walk is how to walk, don't say I want everything is cut leg in turn,

How, then, with the stick before you answer is an answer, before somebody else use gateway, routing, with you it's the same name who you, then you call logic gateway, or you can call routing or action, is don't make the universal solution, you let them remain independent, and then use the gateway, routing, bus topic, also into a named pipe, pipeline pipe and line (the asp.net here is not the core, he find the control of the entire pipeline pipe how, how he various so-called middleware based on different things to deal with different things, just don't say the middleware, let us with you and I said asp.net core of this universal solution to write case 1 control1, case2 control2, obviously not, he just told you inherit controlbase, then according to the rule implementation)

Well, crap here, you understand

In us why Ocelot gateway or waste legs, dig eyes in turn push, push the radar! Because the overall is somebody else's operations of live, operations have their own martial arts and weapon, the somebody else there is wireless wondrous, automation tools, automated deployment tools, performance monitoring and analysis tools, link monitoring tools, log collection and analysis tools, alarm plans and disposal tools, you let people play this, not at fighting skill

CodePudding user response:

So you this thing, according to the pipeline can not, is it part of your current is completely can use

Microsoft, asp.net I temporarily don't want to push the core middleware system, because not clean enough, he to do things too much, some confused

So we start with a relatively clean start to the basis of

https://github.com/ipvalverde/PipelineNet

Var pipeline=new Pipeline. Add. Add. Add. The add (typeof (3))//note he has this, I specially wrung out, because of his support registration type, so this we also need not such a actually a handwritten, we can directly when start to put all achieved the specific interface type with reflection found out, then add in circulation, so that no matter how much you write back is ok, so it can achieve the above said, inheritance, and don't worry about anything case


As for the action

Looking at his example

Public class PersonWithOddId: IAsyncMiddleware//this method parameter PersonModel is your that, we call context parameter
{
Public async Task Run (PersonModel context, Func ExecuteNext)
{
If (context. Id. HasValue & amp; & The context. Id. The Value % 2!=0)//here you see, he will be according to the context parameter to do their own things
{
The context. Level=2;

//here, here is that if I do, don't do, then return directly, it is good to do not do the following
}
Await executeNext (context);//here it is to the next action to decide you want to do
}
}