> The problem is that the current API basically blocks on a request, doesn't > have support for anything but KSKs, and so on.
The API should block on request. That's why we have threading. I certainly don't want to have to do a request and then keep checking to see if the request has come in yet. > I'm not sure what the > new API will look like - to request, you'll create a RequestKSK or > RequestCHK object, which at some future point will tell you that it > suceeded/failed. Either as an attribute which you can check, or a callback. Yuck. I just want a function which I can call which will return to me an item or throw an exception. Just like in the good old days when Travis was using a dictionary to simulate Freenet. I don't see why you'd want to make requests non-blocking. I'm using the blocking request right now and have a perfectly nice NNTP gateway server which never waits for requests. It updates its cache of messages in the background through the beauty of launching a new thread for each request. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
