# Yukon design megathread

**URL:** <https://forum.opencyphal.org/t/yukon-design-megathread/390>\
**Category:** Yukon\
**Created:** [March 12, 2019, 8:26pm UTC](https://forum.opencyphal.org/t/yukon-design-megathread/390 "2019-03-12T20:26:06Z")\
**Posts on this page:** 1\
**Showing post:** 82

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [May 7, 2019, 5:08pm UTC](https://forum.opencyphal.org/t/yukon-design-megathread/390/82 "2019-05-07T17:08:54Z")

</div>

> [@Zarkopafilis](#):
>
> Does being able to POST new configuration and restart yukon backend sound like a new idea?

Sure, but we don’t need to _restart the whole backend_. We just need to instantiate a new `pyuavcan.Node` and destroy the old one. We may even keep the interfaces running, but I am not sure (I’m yet to get to that part).

> [@Zarkopafilis](#):
>
> What’s the purpose of the file server on the old gui\_tool?

We need the file server for firmware updates:

> <https://github.com/OpenCyphal/public_regulated_data_types/blob/3baa2e90a0e8c7b660a2deda8f9a541877ed58e5/uavcan/node/435.ExecuteCommand.0.1.uavcan#L18-L49>

Which reminds me that if the server is running on a different machine, the user should be able to somehow upload the file to the server via the GUI.

The file server may be useful by itself irrespective of the firmware update feature.

* * *

Side note:

> [@Zarkopafilis](#):
>
> The last remaining things to chat about design and ux considerations would be the dynamic node allocation widget, message logging and subscribing widget.

[We don’t say “dynamic allocation” anymore](https://forum.opencyphal.org/t/on-subject-service-id-ranges/195/5). We say “plug-and-play” instead, because it reflects the semantics better.

---

_[View the full topic](https://forum.opencyphal.org/t/yukon-design-megathread/390)._