834a5a0521
* Swapped v1 with v4 UUID as requestId when logging no issue v1 UUID are based on current time and the hardware MAC address of the machine where they are being generated. As such they have much more complex semantics than v4 UUIDs which are simply randomly generated. Unless there's a specific requirement for the special semantics of v1 UUIDs it is simpler and less error prone to simply go for v4 UUIDs whenever just a unique identifier is needed. * Swapped v1 with v4 UUID when creating a temporary contentFolder no issue v1 UUID are based on current time and the hardware MAC address of the machine where they are being generated. As such they have much more complex semantics than v4 UUIDs which are simply randomly generated. Unless there's a specific requirement for the special semantics of v1 UUIDs it is simpler and less error prone to simply go for v4 UUIDs whenever just a unique identifier is needed. * Swapped v1 with v4 UUID when creating a temporary exportFolder no issue v1 UUID are based on current time and the hardware MAC address of the machine where they are being generated. As such they have much more complex semantics than v4 UUIDs which are simply randomly generated. Unless there's a specific requirement for the special semantics of v1 UUIDs it is simpler and less error prone to simply go for v4 UUIDs whenever just a unique identifier is needed. |
||
|---|---|---|
| .. | ||
| admin | ||
| api | ||
| shared | ||
| site | ||
| index.js | ||
| parent-app.js | ||