Tornado 4.5 Documentation
Tornado web application is done in subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define define a BaseHandler class that overrides methods such as write_error and get_current_user and then subclass your own BaseHandler instead of RequestHandler for all your specific handlers. Handling request different template paths for different handlers). To load templates from a non-filesystem location, subclass tornado.template.BaseLoader and pass an instance as the template_loader application setting. Compiled0 码力 | 333 页 | 322.34 KB | 1 年前3
Tornado 4.5 Documentation
Tornado web application is done in subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define define a BaseHandler class that overrides methods such as write_error and get_current_user and then subclass your own BaseHandler instead of RequestHandler for all your specific handlers. Handling request different template paths for different handlers). To load templates from a non-filesystem location, subclass tornado.template.BaseLoader and pass an in- stance as the template_loader application setting.0 码力 | 222 页 | 833.04 KB | 1 年前3
Tornado 5.1 Documentation
Tornado web application is done in subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define define a BaseHandler class that overrides methods such as write_error and get_current_user and then subclass your own BaseHandler instead of RequestHandler for all your specific handlers. Handling request different template paths for different handlers). To load templates from a non-filesystem location, subclass tornado.template.BaseLoader and pass an in- stance as the template_loader application setting.0 码力 | 243 页 | 895.80 KB | 1 年前3
Tornado 5.1 Documentation
Tornado web application is done in subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define define a BaseHandler class that overrides methods such as write_error and get_current_user and then subclass your own BaseHandler instead of RequestHandler for all your specific handlers. Handling request different template paths for different handlers). To load templates from a non-filesystem location, subclass tornado.template.BaseLoader and pass an instance as the template_loader application setting. Compiled0 码力 | 359 页 | 347.32 KB | 1 年前3
Tornado 6.5 DocumentationTornado web application is done in subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define define a BaseHandler class that overrides methods such as write_error and get_current_user and then subclass your own BaseHandler instead of RequestHandler for all your specific handlers. Handling request different template paths for different handlers). To load templates from a non-filesystem location, subclass tornado.template.BaseLoader and pass an instance as the template_loader application setting. Compiled0 码力 | 272 页 | 1.12 MB | 3 月前3
Tornado 6.1 Documentation
Tornado web application is done in subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define define a BaseHandler class that overrides methods such as write_error and get_current_user and then subclass your own BaseHandler instead of RequestHandler for all your specific handlers. Handling request different template paths for different handlers). To load templates from a non-filesystem location, subclass tornado.template.BaseLoader and pass an in- stance as the template_loader application setting.0 码力 | 245 页 | 904.24 KB | 1 年前3
Tornado 6.0 Documentation
Tornado web application is done in subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define define a BaseHandler class that overrides methods such as write_error and get_current_user and then subclass your own BaseHandler instead of RequestHandler for all your specific handlers. 6.1. User’s guide different template paths for different handlers). To load templates from a non-filesystem location, subclass tornado.template.BaseLoader and pass an in- stance as the template_loader application setting.0 码力 | 245 页 | 885.76 KB | 1 年前3
Tornado 6.4 Documentation
Tornado web application is done in subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define define a BaseHandler class that overrides methods such as write_error and get_current_user and then subclass your own BaseHandler instead of RequestHandler for all your specific handlers. Handling request different template paths for different handlers). To load templates from a non-filesystem location, subclass tornado.template.BaseLoader and pass an instance as the template_loader application setting. Compiled0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.2 Documentation
Tornado web application is done in subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define define a BaseHandler class that overrides methods such as write_error and get_current_user and then subclass your own BaseHandler instead of RequestHandler for all your specific handlers. Handling request different template paths for different handlers). To load templates from a non-filesystem location, subclass tornado.template.BaseLoader and pass an instance as the template_loader application setting. Compiled0 码力 | 260 页 | 1.06 MB | 1 年前3
Tornado 6.4 Documentation
Tornado web application is done in subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define define a BaseHandler class that overrides methods such as write_error and get_current_user and then subclass your own BaseHandler instead of RequestHandler for all your specific handlers. Handling request different template paths for different handlers). To load templates from a non-filesystem location, subclass tornado.template.BaseLoader and pass an instance as the template_loader application setting. Compiled0 码力 | 268 页 | 1.09 MB | 1 年前3
共 20 条
- 1
- 2













