| 1 |
On Tue, 16 May 2017 04:58:44 +0200 |
| 2 |
Kai Krakow <hurikhan77@×××××.com> wrote: |
| 3 |
|
| 4 |
> If this is the underlying (and perfectly legitimate) problem, you need |
| 5 |
> to deploy a solution that's most easy for your users and not for you. |
| 6 |
> That may involve a custom transfer solution where they simply can drop |
| 7 |
> files to. The underlying technology is then up to you: Use what is |
| 8 |
> appropriate. |
| 9 |
|
| 10 |
If users have difficulty with keyboard/mouse, but you find a client |
| 11 |
that's to their liking, but they're not necessarily capable of |
| 12 |
configuring for your service, it might be possible to find a "config |
| 13 |
file" for that client which they can fetch over plain ol' http:// with |
| 14 |
whatever tools they usually use for downloading http:// things. |
| 15 |
|
| 16 |
If the program they use doesn't have a "launcher config thinger" but |
| 17 |
can be imagined to use whatever transfer technology you choose ( ssh ), |
| 18 |
and you don't fancy writing a dedicated client, it could be simpler to |
| 19 |
write an installer for them, which configures their existing client for |
| 20 |
your service. |
| 21 |
|
| 22 |
But I'd imagine lots of confusion is emanating from this list due to |
| 23 |
the requirements not being entirely clear/obvious. |
Archives