> The problem is that if we hard-code the GUI wrapper to detect the limit, > then the various wrappers may not get updated when the limit changes. > The solution is for the wrapper to somehow query for the limit, but that > means setting up a query mechanism. Much as my user-centric heart pines > for the best possible GUI, even I admit that for now we should just > intercept the error at the lowest level (where the failure occurs), and > pass a sensible message back up to the top.
It would be pretty trivial to add a command line option to the clients to print out important information in an easily parsable format. So you could get the client version, protocol version, build number, maximum file size limit and anything else you think the GUIs might want to know. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
