PyWebIO v0.3.0 使用手册/io API与后端进行通讯。 例如你将PyWebIO静态文件托管到 /A/B/C/(.*) 路径下,那么你需要将 PyWebIO API的路由绑定到 /A/B/C/io 处; 你也可以在PyWebIO前端页面使用 pywebio_api Url参数来指定PyWebIO后端API地址, 例如 /A/B/C/? pywebio_api=/D/pywebio 将PyWebIO后端API地址设置到了 /D/pywebio 处。 pywebio_api 参数可以使用相对地址、绝对地址甚至指定其他服务器。 如果你不想自己托管静态文件,你可以使用PyWebIO的Github Page页面: https://wang0618.github.io/PyWebIO/pywebio/html/?pywebio_api= ,需要在 页面上通过 pywebio_api 参数传入后端API地址,并且将 https://wang0618 https://wang0618.github.io 加入 allowed_origins 列表中(见下文说明)。 警告 需要注意 pywebio_api 参数的格式: 相对地址可以为 ./xxx/xxx 或 xxx/xxx 的相对地址格式。 绝对地址以 / 开头,比如 /aaa/bbb . 指定其他服务器需要使用完整格式: http://example.com:5000/aaa/io 、 ws://example0 码力 | 72 页 | 8.55 MB | 1 年前3
PyWebIO v0.3.0 使用手册默认通过当前页面的同级的 ./io API 与后端进行通讯。 例如你将 PyWebIO 静态文件托管到 /A/B/C/(.*) 路径下,那么你需要将 PyWebIO API 的路由绑定到 /A/ B/C/io 处;你也可以在 PyWebIO 前端页面使用 pywebio_api Url 参数来指定 PyWebIO 后端 API 地址,例 如 /A/B/C/?pywebio_api=/D/pywebio 将 将 PyWebIO 后端 API 地址设置到了 /D/pywebio 处。 pywebio_api 参数可以使用相对地址、绝对地址甚至指定其他服务器。 如果你不想自己托管静态文件,你可以使用 PyWebIO 的 Github Page 页面: https://wang0618.github. io/PyWebIO/pywebio/html/?pywebio_api= ,需要在页面上通过 pywebio_api pywebio_api 参数传入后端 API 地址,并且将 https://wang0618.github.io 加入 allowed_origins 列表中(见下文说明)。 4.1. User’s guide 21 PyWebIO, 发布 0.3.0 警告: 需要注意 pywebio_api 参数的格式: • 相对地址可以为 ./xxx/xxx 或 xxx/xxx 的相对地址格式。 • 绝对地址以0 码力 | 70 页 | 1.41 MB | 1 年前3
PyWebIO v1.6.2 Documentationdescribed below, which is different from the traditional web development pattern that backend implement api and frontend display content. In PyWebIO, you only need to write code in Python. In fact, the way like writing a console program, except that the terminal here becomes a browser. Using the imperative API provided by PyWebIO, you can simply call put_text(), put_image(), put_table() and other functions to When using Flask, request is instance of flask.Request [https://flask.palletsprojects.com/en/1.1.x/api/#incoming-request-data] When using Django, request is instance of django.http.HttpRequest [https://docs0 码力 | 148 页 | 7.46 MB | 1 年前3
PyWebIO v1.5.1 Documentationdescribed below, which is different from the traditional web development pattern that backend implement api and frontend display content. In PyWebIO, you only need to write code in Python. In fact, the way like writing a console program, except that the terminal here becomes a browser. Using the imperative API provided by PyWebIO, you can simply call put_text(), put_image(), put_table() and other functions to When using Flask, request is instance of flask.Request [https://flask.palletsprojects.com/en/1.1.x/api/#incoming-request-data] When using Django, request is instance of django.http.HttpRequest [https://docs0 码力 | 144 页 | 7.46 MB | 1 年前3
PyWebIO v1.6.1 Documentationdescribed below, which is different from the traditional web development pattern that backend implement api and frontend display content. In PyWebIO, you only need to write code in Python. In fact, the way like writing a console program, except that the terminal here becomes a browser. Using the imperative API provided by PyWebIO, you can simply call put_text(), put_image(), put_table() and other functions to When using Flask, request is instance of flask.Request [https://flask.palletsprojects.com/en/1.1.x/api/#incoming-request-data] When using Django, request is instance of django.http.HttpRequest [https://docs0 码力 | 148 页 | 7.46 MB | 1 年前3
PyWebIO v1.6.3 Documentationdescribed below, which is different from the traditional web development pattern that backend implement api and frontend display content. In PyWebIO, you only need to write code in Python. In fact, the way like writing a console program, except that the terminal here becomes a browser. Using the imperative API provided by PyWebIO, you can simply call put_text(), put_image(), put_table() and other functions to When using Flask, request is instance of flask.Request [https://flask.palletsprojects.com/en/1.1.x/api/#incoming-request-data] When using Django, request is instance of django.http.HttpRequest [https://docs0 码力 | 150 页 | 7.46 MB | 1 年前3
PyWebIO v1.6.0 Documentationdescribed below, which is different from the traditional web development pattern that backend implement api and frontend display content. In PyWebIO, you only need to write code in Python. In fact, the way like writing a console program, except that the terminal here becomes a browser. Using the imperative API provided by PyWebIO, you can simply call put_text(), put_image(), put_table() and other functions to When using Flask, request is instance of flask.Request [https://flask.palletsprojects.com/en/1.1.x/api/#incoming-request-data] When using Django, request is instance of django.http.HttpRequest [https://docs0 码力 | 148 页 | 7.46 MB | 1 年前3
PyWebIO v1.5.2 Documentationdescribed below, which is different from the traditional web development pattern that backend implement api and frontend display content. In PyWebIO, you only need to write code in Python. In fact, the way like writing a console program, except that the terminal here becomes a browser. Using the imperative API provided by PyWebIO, you can simply call put_text(), put_image(), put_table() and other functions to When using Flask, request is instance of flask.Request [https://flask.palletsprojects.com/en/1.1.x/api/#incoming-request-data] When using Django, request is instance of django.http.HttpRequest [https://docs0 码力 | 144 页 | 7.46 MB | 1 年前3
PyWebIO v1.5.0 Documentationdescribed below, which is different from the traditional web development pattern that backend implement api and frontend display content. In PyWebIO, you only need to write code in Python. In fact, the way like writing a console program, except that the terminal here becomes a browser. Using the imperative API provided by PyWebIO, you can simply call put_text(), put_image(), put_table() and other functions to When using Flask, request is instance of flask.Request [https://flask.palletsprojects.com/en/1.1.x/api/#incoming-request-data] When using Django, request is instance of django.http.HttpRequest [https://docs0 码力 | 144 页 | 7.46 MB | 1 年前3
PyWebIO v1.7.0 Documentationdescribed below, which is different from the traditional web development pattern that backend implement api and frontend display content. In PyWebIO, you only need to write code in Python. In fact, the way like writing a console program, except that the terminal here becomes a browser. Using the imperative API provided by PyWebIO, you can simply call put_text(), put_image(), put_table() and other functions to When using Flask, request is instance of flask.Request [https://flask.palletsprojects.com/en/1.1.x/api/#incoming-request-data] When using Django, request is instance of django.http.HttpRequest [https://docs0 码力 | 149 页 | 7.46 MB | 1 年前3
共 86 条
- 1
- 2
- 3
- 4
- 5
- 6
- 9













