Wording improvements for appservices
This commit is contained in:
parent
7caad61b86
commit
c8ba2e098c
2 changed files with 4 additions and 4 deletions
|
@ -33,9 +33,9 @@ paths:
|
||||||
This API is called by the homeserver when it wants to push an event
|
This API is called by the homeserver when it wants to push an event
|
||||||
(or batch of events) to the application service.
|
(or batch of events) to the application service.
|
||||||
|
|
||||||
The application service should take care to ensure that it handles
|
Note that the application service should distinguish state events
|
||||||
state events by the presence of a ``state_key``, not by the event
|
from message events via the presence of a ``state_key``, rather than
|
||||||
type.
|
via the event type.
|
||||||
operationId: sendTransaction
|
operationId: sendTransaction
|
||||||
parameters:
|
parameters:
|
||||||
- in: path
|
- in: path
|
||||||
|
|
|
@ -224,7 +224,7 @@ need to be able to adjust the ``origin_server_ts`` value to do this.
|
||||||
|
|
||||||
Inputs:
|
Inputs:
|
||||||
- Application service token (``as_token``)
|
- Application service token (``as_token``)
|
||||||
- Desired timestamp in milliseconds since the unix epoch
|
- Desired timestamp (in milliseconds since the unix epoch)
|
||||||
|
|
||||||
Notes:
|
Notes:
|
||||||
- This will only apply when sending events.
|
- This will only apply when sending events.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue