On Fri, 31 Mar 2006 19:49:29 +0000 (UTC), Matthew Toseland <toad at amphibian.dyndns.org> wrote:
[...] > > (2) Any kind of private download that should be displayable (but not > > modifyable) by other apps. For example Frost downloads if Frost is > > configured to handle its downloads itself. > > Don't we want it to be possible to pause these/change priority on them? Yes, that would be useful. Perhaps also being able to abort it. But the more I think about (2) the more obsolete it seems. Maybe we don't need it at all. (I was too much thinking of different apps being like different users, hence the "you may watch it, but not touch it" idea. This might still be useful for true multi-user environments accessing a common node, but for now I think - forget it) [...] > That's not a bad idea. Of course it's necessary for there to be multiple > central monitoring apps. FUQID and a queue manager page on Fproxy, for > example. Agreed, FProxy should at least be able to display the GQ and allow the user to abort requests and save data from ReturnType=direct. [...] > Given this understanding of (3), is there any need for (2) ? I don't think so (for the alpha); see above. > > (*)(Generally, AllData should only be sent by the node in reply to a (not > > yet existing) "GetData" message, rather than automatically - at least for > > global requests) > > We can keep it as it is now for local requests. Clients shouldn't keep > large amounts of data on the node unless they have to, it's anti-social. :) Keeping it the way it is for non-global requests is fine. For global requests, the problem I see is: User queues up a bunch of downloads and goes to sleep. The next day he fires up Fuqid; upon starting to WatchGlobal Fuqid will instantly get flooded by maybe gigabytes of AllData that are streamed from the node through the local network. Not only would this slow down things, but it is useless too, because Fuqid cannot use any of the data yet (it just wouldn't know what to do with it). (And if it is a global request, you need to keep the data on the node anyway until it is RemovePersistentRequest'ed) > > Preferably all clients should detect (or let the user configure) if the > > node is local or not. > > How can we do this? Clients could just do it very simply; they need to be able to configure the FCP2 address and port anyway, so if the address resolves to anything different than 127.0.0.1, just ask the user "Is your node on the same PC?" and remember his answer until he reconfigures the FCP2 address. mxbee -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 168 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20060331/f5ce1933/attachment.pgp>
