#Services
Services are entirely built into the Flok kernel. If you need custom actions for your services, they must be created as a driver and then
you must adhere to the services API.

###Request
You initiate a service request via `Request`. This may be called only in the controller at this time. This macro takes several parameters
parameters, all of which must either be strict variable names or double quoted strings:

  * `Request(name, info, event_name)`
    * `name` - The name of the service you are making a request from
    * `info` - The information to give the service
    * `event_name` - The name of the event when a callback occurs

Callbacks are handled by redirecting them through the [event](./mod/event.md) interface `int_event`.  You should register with `reg_evt` to receive
events back from a service. The request itself is not made via the event system, only the response is.  This may seem a little odd because normally
events come in from the outside while this is an internally generated event.

###Request API
Registering a service involves adding files to the `./app/kern/services` folder. All *ruby* files in this folder are used in the compilation of 
services. You declare services in the following format. Your service should not depend on anything except particular module functions.

```
service("rest") do
  on_init %{
    #Code inserted here is put into the global space, add initialization
    #procedures, functions that need to be called, etc.
    #
    #You may use the function respond(info) within here to 

    #Store the in-progress requests as a list of hashes
    #that contain an array in the order of [event_pointer, evenct_name]
    var service_rest_tp_to_einfo = {}

    function service_rest_callback(tp, success, info) {
      //Lookup event info
      var einfo = service_rest_tp_to_einfo[tp];

      //Send info back to service
      int_event(einfo[0], einfo[1], {:success => success, :info => info});

      //Remove entries in telepointer table and rest service info
      tel_del(tp);
      delete service_rest_tp_to_einfo[tp];
    }
  }

  on_request %{
    #Code that handles a payload goes here.
    #You have access to `info`, `ep`, and `ename` which was given in the Request macro

    //Create a GET request that will respond to the telepointer
    var tp = tel_reg(service_rest_callback);

    //Now register the event information to respond to when a callback is received
    service_rest_tp_to_einfo[tp] = [ep, ename]

    //Start the request
    SEND("net", "if_net_req", "GET", info.url, info.params, tp)
  }
end
```

This is then compiled down to
```js
//***************************************
//on_init code is appended to the outside
//....
//***************************************

//Your request code is put inside a function
function service_rest_req(info, ep, ename) {
  //on_request code
}
```