{"id":5260,"date":"2016-10-27T14:03:36","date_gmt":"2016-10-27T14:03:36","guid":{"rendered":"http:\/\/www.gencayyildiz.com\/blog\/?p=5260"},"modified":"2016-10-27T14:03:36","modified_gmt":"2016-10-27T14:03:36","slug":"asp-net-mvcde-httphandler-olusturma","status":"publish","type":"post","link":"https:\/\/www.gencayyildiz.com\/blog\/asp-net-mvcde-httphandler-olusturma\/","title":{"rendered":"Asp.NET MVC’de HttpHandler Olu\u015fturma"},"content":{"rendered":"
<\/div>\n

Merhaba,<\/p>\n

Asp.NET MVC projelerinde gelen \u00e7o\u011fu talebi Controller katman\u0131nda kar\u015f\u0131lamakta ve kullan\u0131c\u0131ya gerekli \u00e7\u0131kt\u0131y\u0131 View katman\u0131nda g\u00f6stermekteyiz. Haliyle amac\u0131m\u0131z ne olursa olsun gelecek t\u00fcm talepleri kar\u015f\u0131layabilmek i\u00e7in birer Controller ve View’e ihtiyac\u0131m\u0131z olmaktad\u0131r. Genel ge\u00e7er al\u0131\u015fkanl\u0131klar bizi fark\u0131nda olmadan b\u00f6yle \u015fartland\u0131rm\u0131\u015f olsada ger\u00e7ekte hi\u00e7te b\u00f6yle bir zorunluluk bulunmamaktad\u0131r. Bu i\u00e7eri\u011fimizde Asp.NET ve Asp.NET MVC mimarilerinde t\u00fcm Page, Controller ve HttpHandler’lar\u0131 kapsayan ve yap\u0131lan t\u00fcm taleplerin tetikledi\u011fi IHttpHandler aray\u00fcz\u00fc taraf\u0131ndan bir HttpHandler olu\u015fturmay\u0131 ve bu Handler’a bir route ayarlamay\u0131 g\u00f6rece\u011fiz. \u0130\u015fte bu IHttpHandler aray\u00fcz\u00fc sayesinde Controller ve View’e ihtiya\u00e7 duymaks\u0131z\u0131n gelen talepleri kar\u015f\u0131layacak, ard\u0131ndan kullan\u0131c\u0131lara gerekli sonu\u00e7lar g\u00f6sterilebilecektir.<\/p>\n

Daha fazla uzatmadan \u00f6rnek bir Asp.NET MVC projesi a\u00e7arak hayali bir senaryoda konuya direkt giri\u015f yapmak istiyorum.<\/p>\n

\u015eimdi a\u015fa\u011f\u0131daki “OrnekRouteHandler.cs” isimli s\u0131n\u0131f\u0131 inceleyiniz.<\/p>\n

\r\n    public class OrnekRouteHandler : IRouteHandler\r\n    {\r\n        public IHttpHandler GetHttpHandler(RequestContext requestContext)\r\n        {\r\n            return new OrnekHandler(requestContext);\r\n        }\r\n    }\r\n<\/pre>\n
G\u00f6rd\u00fc\u011f\u00fcn\u00fcz gibi “OrnekRouteHandler” s\u0131n\u0131f\u0131 “IRouteHandler” interfaceini uygulayan bir s\u0131n\u0131ft\u0131r ve birazdan olu\u015fturaca\u011f\u0131m\u0131z route \u015femas\u0131na talep g\u00f6nderildi\u011fi zaman tetiklenecektir. Dikkat ederseniz bu tetiklenme neticesinde “OrnekHandler” s\u0131n\u0131f\u0131ndan bir nesne olu\u015fturmakta ve geriye return etmektedir. \u015eimdi bu s\u0131n\u0131f\u0131m\u0131z\u0131 olu\u015ftural\u0131m.<\/p>\n
\r\n    public class OrnekHandler : IHttpHandler\r\n    {\r\n        public RequestContext RequestContext { get; set; }\r\n        public OrnekHandler() { }\r\n        public OrnekHandler(RequestContext RequestContext) { this.RequestContext = RequestContext; }\r\n        public bool IsReusable { get; }\r\n\r\n        public void ProcessRequest(HttpContext context)\r\n        {\r\n            \/\/Gelen talebin i\u015flenmesi\/i\u015flemleri\r\n        }\r\n    }\r\n<\/pre>\n
“OrnekHandler” s\u0131n\u0131f\u0131 ise “IHttpHandler” interfaceini uygulayan bir s\u0131n\u0131ft\u0131r. Route \u015femas\u0131na gelen talebi kar\u015f\u0131layacak olan “OrnekRouteHandler” s\u0131n\u0131f\u0131n\u0131n prosed\u00fcrel i\u015flemlerini \u00fcstlenen “OrnekHandler” s\u0131n\u0131f\u0131, i\u00e7erisinde \u00f6rne\u011fi olu\u015fturuldu\u011fu “OrnekRouteHandler” s\u0131n\u0131f\u0131ndan g\u00f6nderilmi\u015f ve constructer taraf\u0131ndan elde edilen RequestContext nesnesini kullanarak “ProcessRequest” metodu i\u00e7erisinde yap\u0131lan talebin kayna\u011f\u0131 hakk\u0131nda yahut ba\u015fka durumlara \u00f6zel i\u015flemler ger\u00e7ekle\u015ftirebilmektedir.<\/p>\n
\u015eunu s\u00f6ylemekte fayda var ki, birazdan olu\u015fturaca\u011f\u0131m\u0131z route \u015femas\u0131n\u0131 tetikledi\u011fimiz anda Controller ve View olmaks\u0131z\u0131n “ProcessRequest” metodu tetiklenecek ve istenen ne ise \u00e7\u0131kt\u0131 olarak elde edilecektir.<\/p>\n
\u015eimdide bu ad\u0131mda route \u015femam\u0131z\u0131 olu\u015ftural\u0131m. “App_Start” klas\u00f6r\u00fc alt\u0131ndaki “RouteConfig.cs” dosyas\u0131na a\u015fa\u011f\u0131daki gibi bir route ekliyoruz.<\/p>\n
\r\n    public class RouteConfig\r\n    {\r\n        public static void RegisterRoutes(RouteCollection routes)\r\n        {\r\n            routes.IgnoreRoute("{resource}.axd\/{*pathInfo}");\r\n\r\n            routes.Add(new Route("laylaylom", new OrnekRouteHandler()));\r\n\r\n            routes.MapRoute(\r\n                name: "Default",\r\n                url: "{controller}\/{action}\/{id}",\r\n                defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }\r\n            );\r\n        }\r\n    }\r\n<\/pre>\n
Evet, dikkat ederseniz “laylaylom” diyerek sallad\u0131\u011f\u0131m bir route \u015femas\u0131 belirlemi\u015f olduk. \u015eimdi gelin projemizi derleyip \u00e7al\u0131\u015ft\u0131ral\u0131m ve “laylaylom” linkine bir talepte bulunal\u0131m.<\/p>\n