You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FDK Context| deadline | generic response, etc. (#16)
* FDK context
* Generic response object
* Support for FN_DEADLINE
* Fixing status codes problem
* Custom response object tests
* Test functions that raising exceptions
- use safe way to recover from exceptions for both JSON/HTTP handlers
- confirm that status codes are set properly for edge cases like deadline
* Cleaning up before release
* Data coercing tests
* Cleanin up comments
* Updating samples
Since release v0.0.3 developer can consume new API to build truly serverless functions
230
+
Since release v0.0.3 developer can consume new API to build truly serverless functions
229
231
without taking care of Docker images, application, etc.
230
232
231
233
```python
@@ -247,29 +249,29 @@ Each function decorated with `@decorator.fn` will become truly serverless and di
247
249
So, how it works?
248
250
249
251
* A developer writes function
250
-
* FDK(Fn-powered app) creates a recursive Pickle v4.0 with 3rd-party dependencies
251
-
* FDK(Fn-powered app) transfers pickled object to a function based on Python3 GPI(general purpose image)
252
-
* FDK unpickles function and its 3rd-party dependencies and runs it
253
-
* Function sends response back to Fn-powered application function caller
252
+
* FDK(Fn - powered app) creates a recursive Pickle v4.0 with 3rd - party dependencies
253
+
* FDK(Fn - powered app) transfers pickled object to a function based on Python3 GPI(general purpose image)
254
+
* FDK unpickles function and its 3rd - party dependencies and runs it
255
+
* Function sends response back to Fn - powered application function caller
254
256
255
-
So, each CPU-intensive functions can be sent to Fn with the only load on networking(given example creates 7kB of traffic between app's host and Fn).
257
+
So, each CPU - intensive functions can be sent to Fn with the only load on networking(given example creates 7kB of traffic between app's host and Fn).
256
258
257
259
258
260
Applications powered by Fn: exceptions
259
261
--------------------------------------
260
262
261
-
Applications powered by Fn are following Go-like errors concept. It gives you full control on errors whether raise them or not.
263
+
Applications powered by Fn are following Go - like errors concept. It gives you full control on errors whether raise them or not.
262
264
```python
263
265
res, err = app.env()
264
266
if err:
265
267
raise err
266
268
print(res)
267
269
268
270
```
269
-
Each error is an instance fn `FnError` that encapsulates certain logic that makes hides HTTP errors and turns them into regular Python-like exceptions.
271
+
Each error is an instance fn `FnError` that encapsulates certain logic that makes hides HTTP errors and turns them into regular Python - like exceptions.
0 commit comments