![]() ![]() Also I want to validate my XAML Islands toolchain, Mile.Xaml, which will be used for the development of NanaZip 2.x. Because I found my current file transfer tool, Free Download Manager, which does not support 125% DPI scaling properly. Several years later, around late 2021, I want to create a remake version of Nagisa. But Nagisa is still meaningful because I won’t create a merged PR for OpenSSL to adding Universal Windows Platform targeting support without implementing Nagisa. Support pushing a download task to the other devices.īut finally Nagisa had been abandoned because I had met a lot of challenges for implementing a file transfer engine with socket broker background tasks in Universal Windows Platform.Support establishing download daemons on IoT devices (like Raspberry Pi).Support get download URI from QR code and texts in images.Support providing HASH value for downloaded files.Support downloading files from multiple URIs.Support WebSocket and WebSocket Secure. ![]() Support HTTP 1.1 and HTTP/2 protocol for HTTP and HTTPS support.Support multi-thread multi-task download.Support resuming broken/dead downloads.Assassin Transfer Engine (An alternative to ).I had made an ambitious plan, and here is the development roadmap: It is mainly developed in C++ 17, with WinRT API, Win32 API, WRL, STL, C++/CX and C++/WinRT for better efficiency and consumes less storage space. In 2017, I had created a project called Nagisa, a file transfer utility designed for Universal Windows Platform. In recent days, I have created a new project called NanaGet, the successor of Nagisa, a lightweight file transfer utility based on aria2 and XAML Islands. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |