Author Topic: ADC 1.0 Released  (Read 13122 times)

0 Members and 1 Guest are viewing this topic.

Offline blastbeat

  • Scripter
  • Fulll Member
  • ******
  • Posts: 64
  • Karma: +16/-0
Re: ADC 1.0 Released
« Reply #25 on: 03 December, 2007, 19:14:29 »
Not only client->client.Imho is not problem to sniff cid, but yes it is harder. Imho registering by user cid it making harder for users... user can remember nick but how much users can remember theyr CID ? When they lost cid, then they lost all they regs  ::)

one could also say its easier to store one pid somewhere then remember many nicknames and passwords ^^



PtokaX forum

Re: ADC 1.0 Released
« Reply #25 on: 03 December, 2007, 19:14:29 »

Offline PPK

  • Administrator
  • Emperor
  • *****
  • Posts: 1 478
  • Karma: +209/-22
  • PtokaX developer
Re: ADC 1.0 Released
« Reply #26 on: 03 December, 2007, 19:37:34 »
True, when user have many nicks then it is improvement ;D
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

Toast

  • Guest
Re: ADC 1.0 Released
« Reply #27 on: 03 December, 2007, 20:51:32 »

Offline Carraya

  • Newbie
  • *
  • Posts: 8
  • Karma: +10/-6
Re: ADC 1.0 Released
« Reply #28 on: 07 January, 2008, 19:13:02 »
6) i am curios how the "nmdc's"  here want to support multiple shares for multiple hubs via protocol? or this isnt important too? with adc its possible, with nmdc not. open up another client is not a solution ;)

I already done this for my client, works on both nmdc and adc :) It's always been possible, and we actually talked about doing it for DCDM years ago, but never did. The idea is to have different shares on different ports, because then you have different listeners for each share and the whole guessing what hub a user is trying to download from is not important because you will have that share only on that port, so even if it guesses hub wrong it will still be from a hub where you have that share, since the request is done on port.

Offline PPK

  • Administrator
  • Emperor
  • *****
  • Posts: 1 478
  • Karma: +209/-22
  • PtokaX developer
Re: ADC 1.0 Released
« Reply #29 on: 07 January, 2008, 22:16:06 »
Nice, good to see that working implementation exist :)
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

Offline elgee

  • Junior Member
  • **
  • Posts: 24
  • Karma: +12/-1
Re: ADC 1.0 Released
« Reply #30 on: 08 January, 2008, 00:21:35 »
I already done this for my client, works on both nmdc and adc :)

And it is working as I been testing this with Carraya's new client.  :D
it is about time is being done, I am sick and tired of running several clients.

Toast

  • Guest
Re: ADC 1.0 Released
« Reply #31 on: 08 January, 2008, 06:05:02 »
Carraya Client ? is he making any clients these days at least i hope not

Offline Carraya

  • Newbie
  • *
  • Posts: 8
  • Karma: +10/-6
Re: ADC 1.0 Released
« Reply #32 on: 08 January, 2008, 09:54:44 »
Carraya Client ? is he making any clients these days at least i hope not

Yeah I am, besides my obvious dislike of you why do you hope not.

Offline bastya_elvtars

  • Forum God
  • ****
  • Posts: 3 730
  • Karma: +173/-7
  • The rock n' roll doctor
    • The FreshStuff3 Site
Re: ADC 1.0 Released
« Reply #33 on: 09 January, 2008, 19:52:43 »
No flamewar here, please. Go to the DCDEV if you want some. ;-)
Everything could have been anything else and it would have just as much meaning.

Offline Naithif

  • Triple Ace
  • **
  • Posts: 199
  • Karma: +32/-13
Re: ADC 1.0 Released
« Reply #34 on: 09 January, 2008, 22:42:25 »
I already done this for my client, works on both nmdc and adc :) It's always been possible, and we actually talked about doing it for DCDM years ago, but never did. The idea is to have different shares on different ports, because then you have different listeners for each share and the whole guessing what hub a user is trying to download from is not important because you will have that share only on that port, so even if it guesses hub wrong it will still be from a hub where you have that share, since the request is done on port.

It's good to see some people still working on NMDC implementations  ;D
Is encypted transfer between clients possible to use on NMDC? I've seen some newer client had such a feature (though it was marked by experimental) but why not ask if pros are here  ::)

Offline PPK

  • Administrator
  • Emperor
  • *****
  • Posts: 1 478
  • Karma: +209/-22
  • PtokaX developer
Re: ADC 1.0 Released
« Reply #35 on: 09 January, 2008, 23:25:52 »
Is encypted transfer between clients possible to use on NMDC?
Yes it is possible ;)
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

Offline Naithif

  • Triple Ace
  • **
  • Posts: 199
  • Karma: +32/-13
Re: ADC 1.0 Released
« Reply #36 on: 10 January, 2008, 00:07:47 »
Thank you  ::)

Offline Carraya

  • Newbie
  • *
  • Posts: 8
  • Karma: +10/-6
Re: ADC 1.0 Released
« Reply #37 on: 10 January, 2008, 09:13:29 »
Even if PPK has answered already, yes it's just as possible to make a $SUPPORT for it in nmdc as it is to make an extension for adc.

Offline blastbeat

  • Scripter
  • Fulll Member
  • ******
  • Posts: 64
  • Karma: +16/-0
Re: ADC 1.0 Released
« Reply #38 on: 10 January, 2008, 14:14:00 »
But no one make it...

Offline Naithif

  • Triple Ace
  • **
  • Posts: 199
  • Karma: +32/-13
Re: ADC 1.0 Released
« Reply #39 on: 10 January, 2008, 15:21:12 »
But how could a client that's already out use secure transfer on NMDC?  ???
I believe not by adding new support, it wouldn't be non-functioning until all clients support it isn't it?

And if it would be possible, and all the requirements are already implemented (if it works on ADC), why it's only ADC?  >:(

Offline PPK

  • Administrator
  • Emperor
  • *****
  • Posts: 1 478
  • Karma: +209/-22
  • PtokaX developer
Re: ADC 1.0 Released
« Reply #40 on: 10 January, 2008, 21:37:12 »
why it's only ADC?  >:(
Afaik in ADC it is now as unfinished extension. I'm sure that after they finish it will be easy to hack it for use in nmdc (i want to do that, only for that fun to show that it is possible in nmdc) :P
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

Offline Archangel_UK

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: ADC 1.0 Released
« Reply #41 on: 10 February, 2008, 16:35:16 »
I already done this for my client, works on both nmdc and adc  It's always been possible, and we actually talked about doing it for DCDM years ago, but never did. The idea is to have different shares on different ports, because then you have different listeners for each share and the whole guessing what hub a user is trying to download from is not important because you will have that share only on that port, so even if it guesses hub wrong it will still be from a hub where you have that share, since the request is done on port.



Carraya

Where is link to client ?

« Last Edit: 10 February, 2008, 16:39:33 by Archangel_UK »

Offline Gnuff?

  • Double Ace
  • *
  • Posts: 121
  • Karma: +21/-1
    • ?????Gnuff?s Hideout??????
Re: ADC 1.0 Released
« Reply #42 on: 10 February, 2008, 21:13:11 »
Quote
Where is link to client ?
It does not exist, yet anyway
Gnuff

Offline Carraya

  • Newbie
  • *
  • Posts: 8
  • Karma: +10/-6
Re: ADC 1.0 Released
« Reply #43 on: 11 February, 2008, 14:36:20 »
Carraya

Where is link to client ?

It's only been released as alpha yet (to a selected audience), so there's not really a publicly available link, but it is however in my dc share (if you can find me on dc). I will post on this forum, when there's a public beta available.



PtokaX forum

Re: ADC 1.0 Released
« Reply #43 on: 11 February, 2008, 14:36:20 »