doc/requests: mention that job description is cached
doc/requests: combine two repetitive paragraphs
doc/requests: use precise format for variables

The double quotes are not actually part of the variable syntax.
doc/requests: add details about variable interpolation
Merge pull request #85 from mgeisler/doc-requests

Add more detail to requests doc about variable interpolation
test: use `send`, not `sendto` on connected socket

According to the Python docs
(https://docs.python.org/2/library/socket.html#socket.socket.sendto),
you should not use `socket.sendto` if a socket is already connected.

Linux (Ubuntu 12.04) seems to be forgiving of this behavior, but when I
run tests on OSX, I get several `socket.error: [Errno 56] Socket is
already connected` errors in the test suite.

This behavior can be demonstrated with the following Python script:

---
import socket

receiver = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
sender = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)

addr = ('127.0.0.1', 27000)
receiver.bind(addr)
sender.connect(addr)

num_bytes = sender.send(b'foo')
print('Received: %s' % receiver.recv(num_bytes))

num_bytes = sender.sendto(b'bar', addr)
print('Received: %s' % receiver.recv(num_bytes))
---

On Linux, this works and the received messages are printed.
On OSX, the `sendto` calls raises a `Socket is already connected` error.
Merge pull request #87 from larsbutler/fix-test-suite-socket-send

test: use `send`, not `sendto` on connected socket
added optional `name` argument to `exe` property

The new job description property `exe.name` is introduced by the patch
It allows user to explicitly set a name for executable (the value of `ARGV[0]`)
The property is optional, if not supplied, the default method for setting `ARGV[0]` will be used
Currently the default is to set it to "node name"
Docs updated.
Merge pull request #89 from pkit/exe_name

added optional `name` argument to `exe` property