Sign in or 
| Version | User | Scope of changes |
|---|---|---|
| Apr 21 2008, 5:57 PM EDT | bennyflint | 4 words added |
| Apr 21 2008, 4:43 PM EDT | bennyflint | 5 words added, 1 word deleted |
Changes
Key: Additions Deletions
In progress.*
namespace ( server-side ): Issued with your developer keys, a namespace is the context in which you will make all API calls to the Wetpaint servers. The namespace allows us to associate users and content with your client application. Typically, a client application will have a single namespace. It is required for all api calls.
ticket: Returned by a login call, a ticket represents an active user session. We use the ticket to identify a user, to authorize her for future ajax api calls, and to determine which editing tools will be made available to the user when she visits your site. A ticket is required for all ajax api calls. If it will help, you can find an example response and the ticket xsd definition here.
*If you are unsure about a term used on the BALCO wiki, and that term is not defined below, please make a comment below and we'll add an explanation.
namespace ( server-side ): Issued with your developer keys, a namespace is the context in which you will make all API calls to the Wetpaint servers. The namespace allows us to associate users and content with your client application. Typically, a client application will have a single namespace. It is required for all api calls.
ticket: Returned by a login call, a ticket represents an active user session. We use the ticket to identify a user, to authorize her for future ajax api calls, and to determine which editing tools will be made available to the user when she visits your site. A ticket is required for all ajax api calls. If it will help, you can find an example response and the ticket xsd definition here.
*If you are unsure about a term used on the BALCO wiki, and that term is not defined below, please make a comment below and we'll add an explanation.
