Indeed in the current version filenames can not contain whitespace. This is a limitation i will fix.
You can download files you publish - localy. this is what i do for testing. Or you can start two Rodi Core using two different ports, for example 31211 and 31210 (command line flag LocalPort followed by port number will do the trick)
for example, ...\java -jar rodi.jar LocalPort 31210
make sure that in the log Rodi reports that it binds to the right port. Publish files on one Rodi Core and try to download using the other.
You can use different initialization scripts (command line flag ConfigurationScript followed by script name)
You can run up to 10 clients (i did not try more than 10) Every client needs about 25M of RAM. CPU consumption is zero if you have enough RAM.
I am not aware of anybody running Rodi, besides you.
Chat room in the design phase exactly for the security reasons you mention. I have some ideas, but it is going to be very very different from IRC or chat in eMule. Imagine that you send UDP packet somewhere and do not expect any answer and not even ack that your message received on the remote side. suddenly you see reply - another UDP packet from some other IP address. packets can be signed (packets from friends/trustees). Signature is the only way to find out who sent this packet. No support for this so far and not a single word in the online documentation.
BT exists without chat room and without search. It takes times - usually 2-3 years (if ever). i am not going to give up the project easily. some projects take tens of years, may be Rodi is one of them.
Meanwhile forums/mail lists is the way to exchange files.
P.S. this page is going to break 1,000 views. there are at least one or two people besides you who reads my musings. funny.
P.S.1 download support in GUI will be ready tomorrow. it's running, but i need time for some polish http://larytet.sourceforge.net/image...leDownload.PNG



LinkBack URL
About LinkBacks
Reply With Quote

Bookmarks