mirror of
				https://github.com/zulip/zulip.git
				synced 2025-11-03 21:43:21 +00:00 
			
		
		
		
	docs: Update links to python-zulip-api project.
We just renamed a bunch of files in that repository.
This commit is contained in:
		@@ -307,7 +307,7 @@ We want to make it easier to deploy **Zulip Readers** on
 | 
			
		||||
Zulip hardware.  The following document talks about how we want to enable this
 | 
			
		||||
from a code structuring standpoint:
 | 
			
		||||
 | 
			
		||||
[Writing contrib bots](https://github.com/zulip/python-zulip-api/blob/master/bots/readme.md)
 | 
			
		||||
[Writing contrib bots](https://github.com/zulip/python-zulip-api/blob/master/zulip_bots/README.md)
 | 
			
		||||
 | 
			
		||||
This document, on the other hand, is more about designing the Zulip backend
 | 
			
		||||
system to support eventual deployment of reader apps on the Zulip server.
 | 
			
		||||
 
 | 
			
		||||
@@ -137,7 +137,7 @@ soon as it attempted to send them to the client; if that specific HTTP
 | 
			
		||||
response didn't reach the client due to a network TCP failure, then
 | 
			
		||||
those events could be lost).
 | 
			
		||||
 | 
			
		||||
[api-bindings-code]: https://github.com/zulip/python-zulip-api/blob/master/zulip/__init__.py
 | 
			
		||||
[api-bindings-code]: https://github.com/zulip/python-zulip-api/blob/master/zulip/zulip/__init__.py
 | 
			
		||||
 | 
			
		||||
The queue servers are a very high-traffic system, processing at a
 | 
			
		||||
minimum a request for every message delivered to every Zulip client.
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user