 Build web application with Golangfiles XML JSON Regexp Templates Files Strings Summary Web services Sockets WebSocket REST RPC Summary Security and encryption CSRF attacks Filter inputs XSS attacks SQL injection Password Response: response data from server to clients. Conn: connections between clients and servers. Handler: Request handling logic and response generation. http package operating mechanism The following corresponding handler: handler := sh.srv.Handler which is the second argument we passed when we called ListenAndServe . Because we passed nil , Go uses its default handler handler = DefaultServeMux0 码力 | 327 页 | 1.63 MB | 1 年前3 Build web application with Golangfiles XML JSON Regexp Templates Files Strings Summary Web services Sockets WebSocket REST RPC Summary Security and encryption CSRF attacks Filter inputs XSS attacks SQL injection Password Response: response data from server to clients. Conn: connections between clients and servers. Handler: Request handling logic and response generation. http package operating mechanism The following corresponding handler: handler := sh.srv.Handler which is the second argument we passed when we called ListenAndServe . Because we passed nil , Go uses its default handler handler = DefaultServeMux0 码力 | 327 页 | 1.63 MB | 1 年前3
 Celery 3.0 Documentationtask failed, the exception and traceback). Results aren’t enabled by default, so if you want to do RPC or keep track of task results in a database you have to configure Celery to use a result backend. This [http://memcached.org], Redis [http://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ0 码力 | 2110 页 | 2.23 MB | 1 年前3 Celery 3.0 Documentationtask failed, the exception and traceback). Results aren’t enabled by default, so if you want to do RPC or keep track of task results in a database you have to configure Celery to use a result backend. This [http://memcached.org], Redis [http://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ0 码力 | 2110 页 | 2.23 MB | 1 年前3
 Celery v4.0.0 Documentationtask failed, the exception and traceback). Results aren’t enabled by default, so if you want to do RPC or keep track of task results in a database you have to configure Celery to use a result backend. This [http://memcached.org], Redis [http://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='amqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ as0 码力 | 2106 页 | 2.23 MB | 1 年前3 Celery v4.0.0 Documentationtask failed, the exception and traceback). Results aren’t enabled by default, so if you want to do RPC or keep track of task results in a database you have to configure Celery to use a result backend. This [http://memcached.org], Redis [http://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='amqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ as0 码力 | 2106 页 | 2.23 MB | 1 年前3
 The Way To Go - 2012/bin/date) .......................................................474 15.9 Remote procedure calls with rpc ..........................................................................474 15.10 Channels over a ...............................................543 20.4.1 Map structure—Creating a simple http-handler .......................................543 20.4.2 Creating the configuration file app.yaml ..... ...................509 Fig 19.1: Handler functions in goto ............................................................................515 Fig 19.2: The Add handler ..................................0 码力 | 629 页 | 4.85 MB | 1 年前3 The Way To Go - 2012/bin/date) .......................................................474 15.9 Remote procedure calls with rpc ..........................................................................474 15.10 Channels over a ...............................................543 20.4.1 Map structure—Creating a simple http-handler .......................................543 20.4.2 Creating the configuration file app.yaml ..... ...................509 Fig 19.1: Handler functions in goto ............................................................................515 Fig 19.2: The Add handler ..................................0 码力 | 629 页 | 4.85 MB | 1 年前3
 Celery v5.0.5 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2315 页 | 2.14 MB | 1 年前3 Celery v5.0.5 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2315 页 | 2.14 MB | 1 年前3
 Celery v5.0.2 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2313 页 | 2.14 MB | 1 年前3 Celery v5.0.2 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2313 页 | 2.14 MB | 1 年前3
 Celery v5.0.1 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2313 页 | 2.13 MB | 1 年前3 Celery v5.0.1 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2313 页 | 2.13 MB | 1 年前3
 Celery v5.0.0 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2309 页 | 2.13 MB | 1 年前3 Celery v5.0.0 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2309 页 | 2.13 MB | 1 年前3
 Celery 3.0 Documentationtask failed, the exception and traceback). Results aren’t enabled by default, so if you want to do RPC or keep track of task results in a database you have to configure Celery to use a result backend. This SQLAlchemy/Django ORM, Memcached, Redis, RPC (RabbitMQ/AMQP), and – or you can define your own. 2.2. Getting Started 21 Celery Documentation, Release 4.0.0 For this example we use the rpc result backend, that sends result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ0 码力 | 703 页 | 2.60 MB | 1 年前3 Celery 3.0 Documentationtask failed, the exception and traceback). Results aren’t enabled by default, so if you want to do RPC or keep track of task results in a database you have to configure Celery to use a result backend. This SQLAlchemy/Django ORM, Memcached, Redis, RPC (RabbitMQ/AMQP), and – or you can define your own. 2.2. Getting Started 21 Celery Documentation, Release 4.0.0 For this example we use the rpc result backend, that sends result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ0 码力 | 703 页 | 2.60 MB | 1 年前3
 Celery v4.1.0 Documentationto choose from: SQLAlchemy/Django ORM, Memcached, Redis, RPC (RabbitMQ/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient messages result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 714 页 | 2.63 MB | 1 年前3 Celery v4.1.0 Documentationto choose from: SQLAlchemy/Django ORM, Memcached, Redis, RPC (RabbitMQ/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient messages result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 714 页 | 2.63 MB | 1 年前3
共 1000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 100














 
  
 