Links - Visit the Forums! - SF.net Project Page - xMule Screenshots Modules · Home · Content · Downloads · Recommend Us · Search · Statistics · Top · Topics · Your Account Who's Online There are currently, 2 guest(s) and 0 member(s) that are online. You are Anonymous user. You can register for free by clicking here

The comments are owned by the poster. We aren't responsible for their content. No Comments Allowed for Anonymous, please register Clarification #2 (Score: 1) by HopeSeekr on Sunday, July 11 @ 22:59:16 CDT (User Info ) Thanks for pointing this out! My original word was "the [core] protocol was extended". Later in the same statement I said "changed the core protocol". What I meant -- obvious in my eyes, at least -- was that eMule 'extended' the protocol and then, as derived from point #2, did *not* consider that possibly people might not implement features right and thus either upload to them any way (as xMule does) or don't download from them either. All I am saying is that a) eMule should do a better job of leading than they are b) eMule should support all clients equally (and if they submit patches to a fork they need to submit patches to the parent as well, obviously), c) they should upload if they download WHICH IS WHY THIS STARTED IN THE FIRST PLACE! and d) they should have a feature to report errors to the clients that caused them, because some of us do not run eMule at all, ever, because we do not believe in using closed systems (closed cvs, closed compiler, closed irc, closed email, closed forums, closed non-whoring input...you name it, with eMule it is *closed*). | Parent Re: Clarification #2 by Nicely on Monday, July 12 @ 08:30:29 CDT

PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL.
PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.03 Seconds