Re: Disable the app subproject (temporarily)?

Hi Peter,

I agree with you that we should disable the calitko.pri subproject since we’re not working on it. However, I think that we should at first focus on some protocol implementation (BitTorrent seems to me as the best choice now) that will use our generic interface so we have something like a simple and working p2p “framework”. Then I’d suggest to re-open the calitko.pri project and try to refactor the application to use our “framework” with some basic generic functionality instead of the old Gnutella code. Then I’d try to add basic BitTorrent functionality (maybe as a some kind of a plugin?), step by step (as you wrote), so the application will be functional and up-to-date. After we have this, we could regularly add some functionality to the tester.pri and right then to the calitko.pri.

I know that it will be actually more difficult because I haven’t elaborated on this too much and I don’t know exactly what the application should do, but what I want to say is that I think that having a generic p2p “framework” is more important than having a more-or-less functional application.

Could you please describe your (concrete) ideas what the application actually should do (or you’re planning it should do)? I’d really appreciate it since I think it will bring more light into my thinking about this topic.

Have a nice day,

Petr

Would you like to post a relpy?


This post is a reply to:
Disable the app subproject (temporarily)?
Dear all, I'm just back from a vacation and now I'm looking forward to doing some Calitko work again! I was thinking recently that in at least in the last 6 months (more...)

Follow-ups:
Re: Disable the app subproject (temporarily)?
Dear All, As a follow-up to Petr's post I'd like to express my vision of Calitko. I'll be looking forward to reading your views on our common aim and the way (more...)