Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Changes In Branch aku-87e374b7e4-rest-docs Excluding Merge-Ins
This is equivalent to a diff from 2cd687d6e6 to 1c7513b4c0
2015-05-30
| ||
00:01 | rest - Tkt [87e374b7e4] - Updated/reworked documentation to be properly doctools. check-in: 2af315d3c6 user: andreask tags: trunk | |
2015-05-29
| ||
23:51 | Completed editing. This looks to be the best do-able without going deep into the code itself. Test suite would be good, also as demo to show the interactions of various options in the generated code, and their influence on runtime behaviour. Closed-Leaf check-in: 1c7513b4c0 user: andreask tags: aku-87e374b7e4-rest-docs | |
00:51 | A bit more editing on the manpage, more structure, and shuffling pieces around. check-in: a4b7ecc9d2 user: andreask tags: aku-87e374b7e4-rest-docs | |
2015-05-28
| ||
05:59 | Ticket [5613c718c2]. Applied patch for review, and editing. Leaf check-in: 4e2b979bcb user: aku tags: tkt-5613c718c2-cwarnings | |
05:40 | Applied patch from ticket. New branch. Not in a state suitable for merging. See comments in the ticket, i.e. [785d2954d4]. check-in: 9aff74cefd user: aku tags: tkt-785d2954d4-jsonc | |
2015-05-27
| ||
21:33 | Adding a new module to implement SCGI server and application functions. check-in: 693c2ee06f user: hypnotoad tags: scgi | |
00:46 | Start fixing up the documentation of package "rest". check-in: f7c45d905d user: andreask tags: aku-87e374b7e4-rest-docs | |
2015-05-26
| ||
23:41 | Keep up to date with trunk check-in: ca4c2acc78 user: andreask tags: huddle-a753cade83 | |
23:06 | fileutil, fileutil::traverse - Ticket [9b52204fea] - Added testcases showing the O(n**2) set of paths based on the doc example structure. Fixed that example and regenerated embedded docs. check-in: 2cd687d6e6 user: andreask tags: trunk | |
22:28 | fileutil, fileutil::traverse - Ticket [9b52204fea] - Documented the O(n**2) issue with traversing pathologically cross-linked directory hierarchies like /sys. Updated embedded documentation. check-in: 4ae879c0ea user: andreask tags: trunk | |
Changes to modules/rest/rest.man.
1 | [comment {-*- tcl -*- doctools manpage}] | > | | | > > > | > > > > > > > > | > | > > > > | | | | | | > > > > > > > > > > > > > > > > > > > > | > | > | | > | | < > | | | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | > > > | > > | > > > | > | > > | > > | > | > > | > > | > > > > > > > > > > > > > > > > > > > > > > > > > > > | > | > > > | > > > > | > > > | > > > > > > > > > > > > > > > > > > > > > > > > > > > | > > > | > > | > > | > | > > > > > > > | > > > > | > | > > > > > > > > > > > > > > | > > > > | > > > > > > | > > > > > > | > > > | > > > > > > > > > > > > > > > > > > > > > > > | > > | > > > > | > > > > | > > > | > > > | > > > > | > > > > > > > > > > > > > > > > | > > > > | > | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | > > | > > | > > | > > > > | > | > > | > > | > > | > > | > > > | > > > | > > > > | > > > | > | | < < < < < < < < < < | < < < < < < < < | | > | < < < < < < < < < < < < < < < < < < < < < < | < > | > > > > | | > | | | | > > | < | > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 | [comment {-*- tcl -*- doctools manpage}] [vset VERSION 1.0.1] [manpage_begin rest n [vset VERSION]] [moddesc {A framework for RESTful web services}] [titledesc {define REST web APIs and call them inline or asychronously}] [require Tcl 8.5] [require rest [opt [vset VERSION]]] [description] There are two types of usage this package supports: [term {simple calls}], and complete [term interfaces]. In an [term interface] you specify a set of rules and then the package builds the commands which correspond to the REST methods. These commands can have many options such as input and output transformations and data type specific formatting. This results in a cleaner and simpler script. On the other hand, while a [term {simple call}] is easier and quicker to implement it is also less featureful. It takes the url and a few options about the command and returns the result directly. Any formatting or checking is up to rest of the script. [section {Simple usage}] In simple usage you make calls using the http method procedures and then check or process the returned data yourself [comment {= = == === ===== ======== ============= =====================}] [comment {= = == === ===== ======== ============= =====================}] [list_begin definitions] [call [cmd ::rest::simple] [arg url] [arg query] [opt [arg config]] [opt [arg body]]] [call [cmd ::rest::get] [arg url] [arg query] [opt [arg config]] [opt [arg body]]] [call [cmd ::rest::post] [arg url] [arg query] [opt [arg config]] [opt [arg body]]] [call [cmd ::rest::head] [arg url] [arg query] [opt [arg config]] [opt [arg body]]] [call [cmd ::rest::put] [arg url] [arg query] [opt [arg config]] [opt [arg body]]] [call [cmd ::rest::delete] [arg url] [arg query] [opt [arg config]] [opt [arg body]]] [para] These commands are all equivalent except for the http method used. If you use [cmd simple] then the method should be specified as an option in the [arg config] dictionary. If that is not done it defaults to [const get]. If a [arg body] is needed then the [arg config] dictionary must be present, however it is allowed to be empty. [para] The [arg config] dictionary supports the following keys [list_begin definitions] [def [const auth]] [def [const content-type]] [def [const cookie]] [def [const format]] [def [const headers]] [def [const method]] [comment {-- TODO -- describe the meaning of the various keys -- }] [list_end] [para] Two quick examples: [para] Example 1, Yahoo Boss: [comment {--- --- --- --- -- ---- --- --- ---}][example { set appid APPID set search tcl set res [rest::get http://boss.yahooapis.com/ysearch/web/v1/$search [list appid $appid]] set res [rest::format_json $res] }][comment {--- --- --- --- -- ---- --- --- ---}] [para] Example 2, Twitter: [comment {--- --- --- --- -- ---- --- --- ---}][example { set url http://twitter.com/statuses/update.json set query [list status $text] set res [rest::simple $url $query { method post auth {basic user password} format json }] }][comment {--- --- --- --- -- ---- --- --- ---}] [list_end] [section {Interface usage}] An interface to a REST API consists of a series of definitions of REST calls contained in an array. The name of that array becomes a namespace containing the defined commands. Each key of the array specifies the name of the call, with the associated configuration a dictionary, i.e. key/value pairs. The acceptable keys, i.e. legal configuration options are described below. After creating the definitions in the array simply calling [cmd rest::create_interface] with the array as argument will then create the desired commands. [para] Example, Yahoo Weather: [comment {--- --- --- --- --- --- --- --- ---}][example { package require rest set yweather(forecast) { url http://weather.yahooapis.com/forecastrss req_args { p: } opt_args { u: } } rest::create_interface yweather puts [yweather::forecast -p 94089] }][comment {--- --- --- --- -- ---- --- --- ---}] [comment { -- TODO -- figure out what these are ! standard methods ? ::${name}::set_static_args [opt args]] }] [comment {= = == === ===== ======== ============= =====================}] [comment {= = == === ===== ======== ============= =====================}] [list_begin definitions] [comment {= = == === ===== ======== ============= =====================}] [call [cmd ::rest::save] [arg name] [arg file]] This command saves a copy of the dynamically created procedures for all the API calls specified in the array variable [arg name] to the [arg file], for later loading. [para] The result of the command is the empty string [comment {= = == === ===== ======== ============= =====================}] [call [cmd ::rest::describe] [arg name]] This command prints a description of all API calls specified in the array variable [arg name] to the channel [const stdout]. [para] The result of the command is the empty string. [comment {= = == === ===== ======== ============= =====================}] [call [cmd ::rest::parameters] [arg url] [opt [arg key]]] This command parses an [arg url] query string into a dictionary and returns said dictionary as its result. [para] If [arg key] is specified the command will not return the entire dictionary, but only the value of that [arg key]. [comment {= = == === ===== ======== ============= =====================}] [call [cmd ::rest::parse_opts] [arg static] [arg required] [arg optional] [arg words]] This command implements a custom parserfor command options. [list_begin arguments] [arg_def dict static] A dictionary of options and their values that are always present in the output. [arg_def list required] A list of options that must be supplied by [arg words] [arg_def list optional] A list of options that may appear in the [arg words], but are not required. The elements must be in one of three forms: [list_begin definitions] [def name] The option may be present or not, no default. [def name:] When present the option requires an argument. [def name:value] When not present use [const value] as default. [list_end] [arg_def list words] The words to parse into options and values. [list_end] [para] The result of the command is a list containing two elements. The first element is a dictionary containing the parsed options and their values. The second element is a list of the remaining words. [call [cmd ::rest::substitute] [arg string] [arg var]] This command takes a [arg string], substitutes values for any option identifiers found inside and returns the modified string as its results. [para] The values to substitute are found in the variable [arg var], which is expected to contain a dictionary mapping from the option identifiers to replace to their values. [emph Note] that option identifiers which have no key in [arg var] are replaced with the empty string. [para] The option identifiers in [arg string] have to follow the syntax [const %...%] where [var ...] may contain any combination of lower-case alphanumeric characters, plus underscore, colon and dash. [comment {= = == === ===== ======== ============= =====================}] [call [cmd ::rest::create_interface] [arg name]] This command creates procedures for all the API calls specified in the array variable [arg name]. [para] The name of that array becomes a namespace containing the defined commands. Each key of the array specifies the name of the call, with the associated configuration a dictionary, i.e. key/value pairs. The legal keys and their meanings are: [list_begin definitions] [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const url]] The value of this [emph required] option must be the target of the http request. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const description]] The value of this option must be a short string describing the call. Default to the empty string, if not specified. Used only by [cmd ::rest::describe]. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const body]] The value of this option indicates if arguments are required for the call's request body or not. The acceptable values are listed below. Defaults to [const optional] if not specified. [list_begin definitions] [def [const none]] The call has no request body, none must be supplied. [def [const optional]] A request body can be supplied, but is not required. [def [const required]] A request body must be supplied. [def [const argument]] This value must be followed by the name of an option, treating the entire string as a list. The request body will be used as the value of that option. [def [const mime_multipart]] A request body must be supplied and will be interpreted as each argument representing one part of a mime/multipart document. Arguments must be lists containing 2 elements, a list of header keys and values, and the mime part body, in this order. [list_end] [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const method]] The value of this option must be the name of the HTTP method to call on the url. Defaults to GET, if not specified. The acceptable values are [const GET], [const POST], and [const PUT], regardless of letter-case. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const copy]] When present the value of this option specifies the name of a previously defined call. The definition of that call is copied to the current call, except for the options specified by the current call itself. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const unset]] When present the value of this option names an option in the current call. This option is removed from the definition. Use this after [const copy]ing an existing definition to remove options, instead of overriding their value. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const headers]] Specification of additional header fields. The value of this option must be a dictionary, interpreted to contain the new header fields and their values. The default is to not add any additional headers. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const content-type]] The value of this option specifies the content type for the request data. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const req_args]] The value of this option is a list naming the required arguments of the call. Names ending in a colon will require a value. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const opt_args]] The value of this option a list naming the arguments that may be present for a call but are not required. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const static_args]] The value of this option a list naming the arguments that are always the same. No sense in troubling the user with these. A leading dash ([const -]) is allowed but not required to maintain consistency with the command line. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const auth]] The value of this option specifies how to authenticate the calls. No authentication is done if the option is not specified. [list_begin definitions] [def [const basic]] The user may configure the [term {basic authentication}] by overriding the procedure [cmd basic_auth] in the namespace of interface. This procedure takes two arguments, the username and password, in this order. [def [const sign]] The value must actually be a list with the second element the name of a procedure which will be called to perform request signing. [list_end] [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const callback]] If this option is present then the method will be created as an [term async] call. Such calls will return immediately with the value of the associated http token instead of the call's result. The event loop must be active to use this option. [para] The value of this option is the name of a procedure which is invoked when the HTTP call is complete. The procedure will receive three arguments, the name of the calling procedure, the status of the result (one of [const OK] or [const ERROR]), and the data associated with the result, in this order. The http request header will be available in that procedure via [cmd {upvar token token}]. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const cookie]] The value of this option is a list of cookies to be passed in the http header. This is a shortcut to the [const headers] option. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const input_transform]] The value of this option is a command prefix or script to perform a transformation on the query before invoking the call. A script transform is wrapped into an automatically generated internal procedure. [para] If not specified no transformation is done. [para] The command (prefix) must accept a single argument, the query (a dictionary) to transform, and must return the modified query (again as dictionary) as its result. The request body is accessible in the transform command via [cmd {upvar body body}]. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const format]] [def [const result]] The value of this option specifies the format of the returned data. Defaults to [const auto] if not specified. The acceptable values are: [list_begin definitions] [def [const auto]] Auto detect between [const xml] and [const json]. [def [const discard]] [def [const json]] [def [const raw]] [def [const rss]] This is formatted as a special case of [const xml]. [def [const tdom]] [def [const xml]] [list_end] [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const pre_transform]] The value of this option is a command prefix or script to perform a transformation on the result of a call ([emph before] the application of the output transform as per [const format]). A script transform is wrapped into an automatically generated internal procedure. [para] If not specified no transformation is done. [para] The command (prefix) must accept a single argument, the result to transform, and must return the modified result as its result. [para] The http request header is accessible in the transform command via [cmd {upvar token token}] [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const post_transform]] The value of this option is a command prefix or script to perform a transformation on the result of a call ([emph after] the application of the output transform as per [const format]). A script transform is wrapped into an automatically generated internal procedure. [para] If not specified no transformation is done. [para] The command (prefix) must accept a single argument, the result to transform, and must return the modified result as its result. [para] The http request header is accessible in the transform command via [cmd {upvar token token}] [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [def [const check_result]] The value of this option must be list of two expressions, either of which may be empty. [para] The first expression is checks the OK condition, it must return [const true] when the result is satisfactory, and [const false] otherwise. [para] The second expression is the ERROR condition, it must return [const false] unless there is an error, then it has to return [const true]. [comment @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@] [list_end] [list_end][comment {-- end of command list --}] [section Examples] [para] Yahoo Geo: [comment {--- --- --- --- -- ---- --- --- ---}][example { set ygeo(parse) { url http://wherein.yahooapis.com/v1/document method post body { arg documentContent } } ygeo::parse "san jose ca" # "san jose ca" will be interpreted as if it were specified as the -documentContent option }][comment {--- --- --- --- -- ---- --- --- ---}] [para] Google Docs: [comment {--- --- --- --- -- ---- --- --- ---}][example { set gdocs(upload) { url http://docs.google.com/feeds/default/private/full body mime_multipart } gdocs::upload [list {Content-Type application/atom+xml} $xml] [list {Content-Type image/jpeg} $filedata] }][comment {--- --- --- --- -- ---- --- --- ---}] [para] Delicious: [comment {--- --- --- --- -- ---- --- --- ---}][example { set delicious(updated) { url https://api.del.icio.us/v1/posts/update auth basic } rest::create_interface flickr flickr::basic_auth username password }][comment {--- --- --- --- -- ---- --- --- ---}] [para] Flickr: [comment {--- --- --- --- -- ---- --- --- ---}][example { set flickr(auth.getToken) { url http://api.flickr.com/services/rest/ req_args { api_key: secret: } auth { sign do_signature } } rest::create_interface flickr proc ::flickr::do_signature {query} { # perform some operations on the query here return $query } }][comment {--- --- --- --- -- ---- --- --- ---}] [section INCLUDED] The package provides functional but incomplete implementations for the following services: [list_begin definitions] [def [const del.icio.us]] [def [const facebook]] [def [const flickr]] [def [const twitter]] [def [const {google calendar}]] [def [const {yahoo boss}]] [def [const {yahoo weather}]] [list_end] Please either read the package's implementation, or use [cmd rest::describe] after loading it for their details. [para] Do not forget developers' documentation on the respective sites either. [include ../common-text/tls-security-notes.inc] [vset CATEGORY rest] [include ../doctools2base/include/feedback.inc] [comment { TOKENS the value is substituted into the url at call time. tokens in the form of %name:default_value% will be an optional argument with a default value. }] [manpage_end] |