![](\"https://user-images.githubusercontent.com/4038732/35308567-17f72930-005d-11e8-9134-c21c741f0cc7.png\")
\n\n \n
\n ![](\"https://user-images.githubusercontent.com/4038732/35308543-0315f870-005d-11e8-82fa-17aede333138.png\")
\n \n\nThe `woven.configure()` method links the back end with the project's pure functions.\n\n```javascript\nwoven.configure(functionsPath, { /* client options */ });\n```\nThe options object accessible through the configure method also allows for developer customizations:\n \n```javascript\nmodule.exports = {\n alwaysClient: false,\n alwaysServer: false,\n dynamicMax: 10000,\n fallback: 'server',\n maxThreads: 12,\n pingSize: 'small',\n}\n```\n\n#### Developer Customization Options:\n\n - **alwaysClient/alwaysServer:** An optimization override to run processes only on the server or the client, as opposed to letting the WovenJS optimal performance heuristic decide. \n\n - **dynamicMax:** WovenJS's dynamic ping is used to determine the data transmission speed of your server->client connection. This property allows you to set a minimum response time in milliseconds. If the dynamic ping is slower than this threshold, the client will be used for processing.\n\n - **fallback:** In the event that the optimization process fails, WovenJS will route to the fallback assigned here. Unless modified by the developer the default fallback is to process on the server.\n\n - **maxThreads:** A developer override to set the maximum # of threads that can be created for a given client (thread number corrosponds with the number of generated Web Workers).\n\n - **pingSize:** Use this property to set an exact size for the dynamic ping data in bytes or choose between WovenJS's preset options: `'tiny'`(100bytes), `'small'`(4kB), `'medium'`(50kB), `'large'`(400kB), or `'huge'`(1MB).\n\n Make sure that your server/application can handle the larger data transfer (400KB-1MB) before using the large/huge ping size presets.\n \n ![](\"https://user-images.githubusercontent.com/4038732/35308546-05bdf154-005d-11e8-9877-ceabb6a07424.png\")
\n\n The `woven.connect()` method is invoked on the client side to establish a connection between the client and the server. \n\n ```javascript\n woven.connect(/* workerFile */);\n ```\n\n `woven.connect()` triggers the WovenJS’s optimize middleware to set the optimization configuration for each client’s connection. Additionally it takes in the reference to the imported Web Workers file so that WovenJS can spawn workers as needed.\n\n ![](\"https://user-images.githubusercontent.com/4038732/35308554-09e7228c-005d-11e8-9329-f49ab7580292.png\")
\n\n WovenJS sends an auto-generated dynamic ping to capture data transmission speed for each client's connection. The dynamic ping should be proportionate to the application's functonality (for example, set the dynamic ping to the size of a JPG for an app that relies heavily on image file transfers). \n \n If the dynamic ping is slower than the `dynamicMax` threshold, the client will be used for processing. If it's faster, the server will be used.\n \n ![](\"https://user-images.githubusercontent.com/4038732/35308551-07f95ea4-005d-11e8-8d81-4b8ade2db02f.png\")
\n \n WovenJS's optimization process evaluates the most performant processing location depending on the hardware, software, and network capabilities of the client-side device. WovenJS will automatically route processing to the server or the client depending on what location will result in the fastest most performant client experience.\n\n ![](\"https://user-images.githubusercontent.com/4038732/35312963-d4709d20-0072-11e8-80f2-57423e8ac1d1.png\")
\n \n Use the `woven.run()` function wherever you want to run one of the functions in your pure functions file. WovenJS will decide where to run the function based on the optimization heuristic. \n\n ```javascript\n woven.run('function name', payload, ...moreArgs)\n .then(output => {\n /* do something with output */\n });\n ```\n \n The first argument passed to `woven.run()` is the name of the function as a string. Next you can pass in any arguments that your function will take. You can pass in as many arguments as you like. `woven.run()` always returns a *promise*, so you can chain `.then()` on to `woven.run()` to utilize the output.\n\n
\n ![](\"https://user-images.githubusercontent.com/4038732/35314686-afd44822-007c-11e8-8fef-92225d5fb4fa.jpg\") \n \n Althea Capra\n \n \n \n | \n \n ![](\"https://user-images.githubusercontent.com/4038732/35314688-affa1d36-007c-11e8-89c2-2492d174b7dc.jpg\") \n \n Erik Larsen\n \n \n \n | \n \n ![](\"https://user-images.githubusercontent.com/4038732/35314689-b00cfc1c-007c-11e8-97b4-b38651546a12.jpg\") \n \n Ryan London\n \n \n \n | \n \n ![](\"https://user-images.githubusercontent.com/4038732/35314687-afe7f82c-007c-11e8-9ef2-99ecd3694e3d.jpg\") \n \n Dale Nogiec\n \n \n \n \n \n \n |