v1.2 is supposed to mark the completion of work on the indexing service as the main topic and include older requests as well.
after v1.2 i may go for an unrelated large topic.
so you put in this thread what you think is relevant to this release.
there are may be several v1.1x releases in between as features are being added and refined.
was: current work (indexing service related up to v1.2.2)
it seems at most within 2 days i'll finish with the work on v1.2 client part, but we may still have v1.1x releases, since i want something final.
as i warned previously on the download page i need to change the indexing service protocol so you'll have to update to use the search service (but i'll tell when exactly).
as i warned previously on the download page i need to change the indexing service protocol so you'll have to update to use the search service (but i'll tell when exactly).
the current search service protocol doesn't notify about the protocol change, so first i'll make a release which does that, so hopefully most users will upgrade before the change will have place. for older versions it will give "Error communicating with the server".
i'll also roll back the trial period back to 15 days since i don't want to mess with adding retrial protection.
it is on the top of the latest feature additions and improvements.
i'm switching to work on the server tomorrow (increasing retention etc).
i'll also roll back the trial period back to 15 days since i don't want to mess with adding retrial protection.
it is on the top of the latest feature additions and improvements.
i'm switching to work on the server tomorrow (increasing retention etc).
i missed one compiler switch, in short the server can run without modification for retention about 50 days.
because the server computer has only 2.5GB memory i've just set it to 40 days (i kept the old header data so it is immediately available). i'll monitor for a short time whether the RAM is enough but it appears to be the case.
with the modification it will give 50 day increments then (like the simplest configuration with modification will give 100 days if i have a computer with enough RAM, a 4GB computer maybe can give about 70 - 75 days, to add 2GB more it will be 100, i think 32 bit system can handle up to 16GB in principle so to install 8GB is feasible, just money)
but i may still change the protocol, although now i'm not sure i'll work on further extending retention or finish the work on the client and release it as v1.2, since later i may be interested in 64 bit server version instead of modifying it for 32 bit, just right now it is not the time since i want to do some other work on the client.
i just wanted to keep it up with news-service, newshosting (they are moving to 40 day retention), UNS and other affordable usenet providers.
because the server computer has only 2.5GB memory i've just set it to 40 days (i kept the old header data so it is immediately available). i'll monitor for a short time whether the RAM is enough but it appears to be the case.
with the modification it will give 50 day increments then (like the simplest configuration with modification will give 100 days if i have a computer with enough RAM, a 4GB computer maybe can give about 70 - 75 days, to add 2GB more it will be 100, i think 32 bit system can handle up to 16GB in principle so to install 8GB is feasible, just money)
but i may still change the protocol, although now i'm not sure i'll work on further extending retention or finish the work on the client and release it as v1.2, since later i may be interested in 64 bit server version instead of modifying it for 32 bit, just right now it is not the time since i want to do some other work on the client.
i just wanted to keep it up with news-service, newshosting (they are moving to 40 day retention), UNS and other affordable usenet providers.
the internet connection was down today (it is not related to the indexing server though), but i finished planned work on the server, little work but i'll be testing it for a short time.
so with the next version the protocol will be updated, it means you will need to upgrade the client to access the indexing service.
so with the next version the protocol will be updated, it means you will need to upgrade the client to access the indexing service.
ok we are mostly ready.
i'll make data backup, will be upgrading versions and restart the server shortly (but not in a hurry
).
it will be some mess, but after you upgrade the version all should run smoothly.
v1.1.8 will be something very close to v1.2, i've decided to release v1.2 and then go to check the possibility of a larger topic, rather than implementing some small requests, since it should save overall development time (eventually including the small requests).
i'll make data backup, will be upgrading versions and restart the server shortly (but not in a hurry
).it will be some mess, but after you upgrade the version all should run smoothly.
v1.1.8 will be something very close to v1.2, i've decided to release v1.2 and then go to check the possibility of a larger topic, rather than implementing some small requests, since it should save overall development time (eventually including the small requests).
ok now, after v1.1.8 release the plan is to see we don't have any problems and then to go on with v1.2, since it is not my intention at all to chew the indexing topic forever.
so if you see any problems let me know, i could try to address it in v1.1.9 or we may have v1.2 right away.
with v1.1.7 the picture was ok.
so if you see any problems let me know, i could try to address it in v1.1.9 or we may have v1.2 right away.
with v1.1.7 the picture was ok.
i've started work on development beyond the v1.2 release, right now mostly conceptual aspects.
there are no enough problems to fix to justify the next release, so until i have more, i'll just move further.
because of the change of course i added a sticky section listing requested (all relatively small) features, so there will be less likelihood they will be lost in oblivion, later i'll add a poll so you can vote for what you want to be added first and i will know what is in most demand when the time will come to work on small features.
there are no enough problems to fix to justify the next release, so until i have more, i'll just move further.
because of the change of course i added a sticky section listing requested (all relatively small) features, so there will be less likelihood they will be lost in oblivion, later i'll add a poll so you can vote for what you want to be added first and i will know what is in most demand when the time will come to work on small features.