Contents

#Deep Link Module (dlink)
The deep linking module allows your application to support start-up URL requests. Many mobile operating systems allow apps to intercept certain URL namespaces which force redirection to an app instead of the default behaviour of a web-browser. This URL on startup feature allows the app to dynamically respond to a URL request from an outside source.

#### Kernel
`int_dlink_notify(url, params)` - An inbound deep-link was intercepted and forwarded. The params are a javascript dictionary of the link parameters and
the url is the base url of the link.  E.g. if the link was `http://google.com/test?my_param=foo` then the url would be `http://google.com/test` and the
`params` are `{my_param: foo}`. This function simple calls the `dlink_notify_handler(url, params)` with the same
parameters. This handler function is currently only ownedowned by the sister-service `dlink`. In the future, we would
like to support the full RFC specification for URI's, but at this time, all the URI libraries are too large to warrant adding the additional bloat especially when
most clients have native ways of decoding URI's.

#### Kernel Spec Interrupts
`get_int_dlink_spec()` - Sends [[0, 1, "get_int_dlink_cb_spec", [url, params]] with the last received request from `int_dlink_notify`.

#### Driver
There is no requests the driver must handle. However, the driver should dispatch the message for the `int_dlink_notify` off the main queue. It should never be dispatched
before the application has fully started up. It is internally asynchronously dispatched, but for safety's sake, it should be dispatched at the soonest, immediately after
the system has loaded.

Version data entries

4 entries across 4 versions & 1 rubygems

Version	Path
flok-0.0.105	docs/mod/dlink.md
flok-0.0.103	docs/mod/dlink.md
flok-0.0.102	docs/mod/dlink.md
flok-0.0.101	docs/mod/dlink.md