Bittorrent and Utorrent merge


Recommended Posts

From what I can see Bit Torrent wants it to implement in other devices (recognises the great oding of ludde).

As for the current uTorrent, it's prettymuch feature full anyways, if they did release a new version (with anything people didn't want) you could just use the old version.

JohnyD's comment on digg.com

Some answers from #uTorrent-questions:

-will uTorrent be ported to Linux?

probably

-how many lines of code is it comprised of?

~50-60K

-will encryption be removed?

no (answered by Bram)

-features most important to you (directed @ Bram)

low memory footprint, code size, cpu usage

-is there any thoughts to an osx client?

(Bram) we plan to produce an up to date osx client, but that's significant porting work

-are there any features that will be removed from uTorrent?

(Bram) we're leaving the uTorrent client mostly alone for now, on the grounds that people like it (further defined 'mostly' as in, not much of anything substantive will change)

-will uTorrent be replacing the original python client?

(Bram) we aren't announcing integration plan details right now

-Bram, are you talking with asus and other router makers for putting uTorent in there?

(Bram) we're talking to lots of people

-will uTorrent ever be open-sourced?

(Bram) not in the forseeable future, but we'll continue to maintain an open source reference implementation

-Bram, you said before that you're not a big fan of protocol header encryption... do you still stand behind this?

(Bram) it isn't much harder for an isp to recognize encrypted headers than unencrypted headers.

-will content be monitored?

(Bram) absolutly not

-does the uTorrent codebase compile on linux today (in your labs?)

(ludde) No

-ludde can't develop anything new for uTorrent?

(ludde) bittorrent inc will do the majority of the development work

-what IDE was uTorrent developed on?

(ludde) Microsoft Visual C++ 6.0 with a few routines written in visual cobol. uTorrent was written in C++ with some tiny chunks of assembly

-will uTorrent continue to be free?

(Bram) utorrent will continue to be available and continue to be free (as in, no cost, not open source)

-Utorrent uses a lot of Windows API's right? Won't that be a problem when porting to *nux/OSX

(ludde) Yes, the UI is tightly bound to Windows APis, however, the core backend is easier to port.

(Bram) the utorrent UI is windows native, so porting that part to osx or linux is a significant amount of work (but planned to be done at some point)

Q: How will uTorrent?s technology be integrated with the current BitTorrent client?

A: Although uTorrent is lightweight, it is missing the patented innovations BitTorrent has made at the protocol level. It is also lacking an implementation for Mac and Linux. We will improve uTorrent in these arenas.


yeah, adding osx would be cool, the backend code will be improved alot with brahem's help (as he wrote it hehe). this should prove for better connectivity and slightly better speeds.

fingers crossed it wont become a retail program and will stay freeware with no banners, ads etc.

great news!!

Im also going to make a backup of my version of uTorrent :D they will screw this up really badly. Soon as the word features comes in the Change log, everyone will go NOOOOOOO and have shout at them :D lets pray they don't use that word.

-will encryption be removed?
no (answered by Bram)

-Bram, you said before that you're not a big fan of protocol header encryption... do you still stand behind this?
(Bram) it isn't much harder for an isp to recognize encrypted headers than unencrypted headers.

got me scared for a while when i saw the news

i need encryption and bram doesn't like it

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.