[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Re: [microdc-devel] Incompatibility with StrongDC++
From: |
Vladimir Chugunov |
Subject: |
RE: Re: [microdc-devel] Incompatibility with StrongDC++ |
Date: |
Fri, 17 Nov 2006 09:48:43 +0300 |
Hello Wong,
>
> Hey Alexey,
>
> first, to not confuse things, we are talking about microdc2
> version 0.13.0, right?
>
> > The commands sequence order in config file is important. It
> seems to me
> > that you have "set sharedir" and then "set listingdir".
> Please, try to
> > change their order.
>
> In 0.13.0 there is no variabe 'sharedir', maybe you meant the
> 'downloaddir'?
> I tried to flip the order of listingdir and downloaddir in
> the config, result is still the same.
Yes, there is a bug in 0.13.0 related to listingdir - I have found it yesterday
and I think I'll fix it today.
> Now to the incompatibility problem:
> > Please enter 'set display all' and try again.
> > It will give more detailed log.
What version of StrongDC do you use? I've tested the 0.13.0 against StrongDC
2.0.2 and there was no problem.
But I've seen now the StrongDC 2.0.3 is available but I don't upgrade yet.
============== logs skipped ================
>
> Two things are interesting here, it seems, that StrongDC++
> detects the "DCPLUSPLUS0.691" in the Lock message from the
> linuxdcpp client and therefor communicates the own
> capabilities " $Supports MiniSlots XmlBZList ADCGet TTHL TTHF
> GetZBlock ZLIG |". This does not happen when requesting the
> filelist from microdc2!
>
> The other thing is that the connection is terminated by
> StrongDC++ right before the filelist upload is initialized
> ("Client: [Incoming][134.96.80.62] $Key
> ^P^PA .00^P 0^P 0^P 0^P 0^P 0^P").
It looks like you are using StrongDC 2.0.3 :-) So there is one big problem with
StrongDC - the authors are useing dcpp client as part of the project but
authors of dcpp are trying to dictate their own ideas. First they've removed
support for NMDC file list, now they are trying to use ADCGET functionality
ONLY. I think the problem is that microdc2 doesn't specify in $Support command
the following: ADCGet TTHL TTHF.
> > > I would like to contribute to this project, however we
> will then need a
> > svn repository.
> > > Alexey, you wrote some cool patches, would you like to
> integrate them in
> > the most recent release?
> > >
> > Yes, i like this idea.
> > Microdc2 it is a project of Vladimir Chugunov. It is better
> to us to ask
> > him.
>
> Good point, Vladimir what do you think about this?
First of all I'm glad to listen there are people wishing to take a part in
microdc2 development because it can reduce my personal task list :-).
Special thanks to Alexey Illarionov who made patch for charset support and
ADCGET functionality - these patches will appear in next release as soon as I
complete merging them into 0.13.0 version.
There are two different ways:
1. Anyone can simply send me the updated sources (or diffs) and I'll integrate
them into main source tree.
2. I've already using CVS installed on corsair626.no-ip.org. I also can provide
an access to the CVS itself on request but in this case we need something like
forum, tasklist or bugzilla to coordinate our work - otherwise there can be
double work when 2 men are writing the same feature or fixing the same bug.
Regards, Vladimir.