Express Your Expectations: A Fast, Compliant JSON Pull Parser for Writing Robust Applicationstc nlohmann RapidJSON Boost.JSON simdjson 0 10 20 30 40 Library Time in ms fully validating pull parser fast, O(1) memory usage implicitly define schema github.com/think-cell/think-cell-library "speaker": true, "talks": [ { "title": "Express your expectations", "subtitle": "A fast, compliant JSON pull parser..." } ] } Jonathan Müller — @foonathan Express your expectations CppCon 2023-10-03 7JSON console.log(object.talks[0].subtitle) console.log(object.foo) Jonathan Müller A fast, compliant JSON pull parser for writing robust applications undefined Jonathan Müller — @foonathan Express your expectations0 码力 | 143 页 | 736.91 KB | 6 月前3
Java EE 企业应用系统设计 - HTTP 请求处理编程browser = request.getHeader("User-Agent"); ▶ int getIntHeader(String name) 1 int size = request.getIntHeader("Content-Length"); ▶ long getDateHeader(String name) 1 long datetime = request.getDateHe getDateHeader("If-Modified-Since"); ▶ Enumeration getHeaderNames() 1 for (Enumeration e = request.getHeaderNames(); e.hasMoreElements(); ) { 2 String headerName = (String) e.nextElement(); 3 System.out.println("Name␣=␣" 参数 1 productSearch.do?productName=Acer 以下代码可以取得以上的参数名为 productName 的数据: 1 String productName = request.getParameter("productName"); 大纲 HTTP 请求内容 Java EE 请求对象 取得请求中包含的提交参数数据 O String[] getParameterValues(String0 码力 | 27 页 | 565.27 KB | 1 年前3
waitress Documentation v3.0.1
race condition that existed when creating a new HTTPChannel. See https://github.com/Pylons/waitress/pull/435 and https://github.com/Pylons/waitress/issues/418 With thanks to Dylan Jay and Dieter Maurer the header values before passing them to the WSGI environ. See https://github.com/Pylons/waitress/pull/434 and https://github.com/Pylons/waitress/issues/432 3.0.0 (2024-02-04) Rename "master" git branch https://github.com/Pylons/waitress/pull/399 Fixed testing of vendored asyncore code to not rely on particular naming for errno's. See https://github.com/Pylons/waitress/pull/397 HTTP Request methods and versions are0 码力 | 55 页 | 56.36 KB | 1 年前3
waitress Documentation v3.0.1requests do not take longer than 30 seconds or Heroku will inform the client that the request failed even though the request is still being processed by Waitress and occupying a thread until it completes. its log messages to the parent logger (the root logger), sending its output to the console when we request a page: 00:50:53,694 INFO [wsgiapp] Returning: Hello World! (content-type: text/plain) 00:50:53 value to be that value, minus any trailing slashes you add, and it will cause the PATH_INFO of any request which is prefixed with this value to be stripped of the prefix. This is useful in proxying scenarios0 码力 | 119 页 | 339.46 KB | 1 年前3
waitress Documentation v2.1.2requests do not take longer than 30 seconds or Heroku will inform the client that the request failed even though the request is still being processed by Waitress and occupying a thread until it completes. its log messages to the parent logger (the root logger), sending its output to the console when we request a page: 00:50:53,694 INFO [wsgiapp] Returning: Hello World! (content-type: text/plain) 00:50:53 value to be that value, minus any trailing slashes you add, and it will cause the PATH_INFO of any request which is prefixed with this value to be stripped of the prefix. This is useful in proxying scenarios0 码力 | 115 页 | 272.79 KB | 1 年前3
waitress Documentation v2.1.1if they contain invalid data we no longer continue in and return a 400 Bad Request. This stops potential HTTP desync/HTTP request smuggling. Thanks to Zhang Zeyu for reporting this issue. See https://github and values such as 0x01 and +01 are no longer supported. This stops potential HTTP desync/HTTP request smuggling. Thanks to Zhang Zeyu for reporting this issue. See https://github.com/Pylons/waitress return a 400 Bad Request when the Content-Length header contains invalid data, such as +10 which would previously get parsed as 10 and accepted. This stops potential HTTP desync/HTTP request smuggling Thanks0 码力 | 53 页 | 58.27 KB | 1 年前3
Pro Git 2nd Edition 2.1.413Flow Advanced Pull Requests GitHub Flavored Markdown Keep your GitHub public repository up-to-date Maintaining a Project Creating a New Repository Adding Collaborators Managing Pull Requests Mentions Services and Hooks The GitHub API Basic Usage Commenting on an Issue Changing the Status of a Pull Request Octokit Summary Git Tools Revision Selection Single Revisions Short SHA-1 Branch References git merge git mergetool git log git stash git tag Sharing and Updating Projects git fetch git pull git push git remote git archive git submodule Inspection and Comparison git show git shortlog0 码力 | 731 页 | 21.49 MB | 1 年前3
Pro Git 2nd Edition 2.1.413 Flow Advanced Pull Requests GitHub Flavored Markdown Keep your GitHub public repository up-to-date Maintaining a Project Creating a New Repository Adding Collaborators Managing Pull Requests Mentions Services and Hooks The GitHub API Basic Usage Commenting on an Issue Changing the Status of a Pull Request Octokit Summary Git Tools Revision Selection Single Revisions Short SHA-1 Branch References git merge git mergetool git log git stash git tag Sharing and Updating Projects git fetch git pull git push git remote git archive git submodule Inspection and Comparison git show git shortlog0 码力 | 691 页 | 13.35 MB | 1 年前3
waitress Documentation v2.1.1requests do not take longer than 30 seconds or Heroku will inform the client that the request failed even though the request is still being processed by Waitress and occupying a thread until it completes. its log messages to the parent logger (the root logger), sending its output to the console when we request a page: 00:50:53,694 INFO [wsgiapp] Returning: Hello World! (content-type: text/plain) 00:50:53 value to be that value, minus any trailing slashes you add, and it will cause the PATH_INFO of any request which is prefixed with this value to be stripped of the prefix. This is useful in proxying scenarios0 码力 | 113 页 | 270.88 KB | 1 年前3
waitress Documentation v2.1.0example See https://github.com/Pylons/waitress/issues/359 and https://github.com/Pylons/waitress/pull/363 In Python 3 OSError is no longer subscriptable, this caused failures on Windows attempting to to find an socket that would work for use in the trigger. See https://github.com/Pylons/waitress/pull/361 Fixed an issue whereby BytesIO objects were not properly closed, and thereby would not get cleaned This led to potential for random memory spikes/memory issues, see https://github.com/Pylons/waitress/pull/358 and https://github.com/Pylons/waitress/issues/357 . With thanks to Florian Schulze for testing/vaidating0 码力 | 52 页 | 57.95 KB | 1 年前3
共 1000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 100













