alexcoder04 / rfap Goto Github PK

This is very likely never to be implemented: to achieve this, the client would have to be listening to the server all the time, so it couldn't send commands.

The only possible solution would be to open a second socket which would have to run in a separate thread that can communicate with the main thread, so the overall design would become much more complicated.

A client with terminal user interface (e.g. curses-based). Maybe in Go, so it's even cross-platform

To save bandwidth, we can add optional compression for large text files. The compression would be turned on if both sides support it and the information about the compression standard would be sent inside the header

(idea for a new implementation)

This app would be able to act as a server as well as a client, but only on the local network (maybe even over Bluetooth?).

Some metadata values are only sent if requested (elements number in directory), some only if info is called, some are sent always.
We should document this more clearly.

If we send files bigger than 16MB, we would need to split them over multiple packets, so we need a specification and implementation of that feature

FUSE allows to write filesystems for Linux in userspace. With PyFUSE, we could build a filesystem based on librfap

Like whether the client/server support compression/collab mode/live mode/...

[headline]

(Although it's a go-server problem, we can discuss it here)

What should we use for the console?
Stdin is not an option, because we don't have a window with the server running open all the time; moreover the server would print messages while you are typing your command, so it wouldn't really work.
A Unix domain socket would be much better, but it's not supported on Windows (does Windows have something like that?).
Another socket listening on localhost? Seems complicated to me.