Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

[rugby-core release]

 [1/3] from: pat665:ifrance at: 9-Feb-2002 14:58


Hi Maarten, I have started testing rugby-core (as I call it). 1. Get-rugby-service needs the :8002 port explicitely, otherwise connection fails.
>> do get-rugby-service http://192.168.1.51
** Access Error: Cannot connect to 192.168.1.51 ** Where: open-proto ** Near: return to-result read/custom proxy reduce
>> do get-rugby-service http://192.168.1.51:8002 >>
2. Rexec needs the :8002 port explicitely, otherwise connection fails.
>> rexec/with [triple 15] http://192.168.1.51
** Access Error: Cannot connect to 192.168.1.51 ** Where: open-proto ** Near: return to-result read/custom proxy reduce
>> rexec/with [triple 15] http://192.168.1.51:8002
== 45
>>
3. As pekr had already mentioned tcp:// is a little bit confusing in serve/with [now] tcp://:9002 In my opinion, it would be more logical to use serve/with [now] 9002 Patrick

 [2/3] from: m::koopmans2::chello::nl at: 9-Feb-2002 16:59


Thanks for the tesing, but this is all known behaviour and won't change for know. --Maarten

 [3/3] from: petr:krenzelok:trz:cz at: 9-Feb-2002 18:10


Maarten Koopmans wrote:
>Thanks for the tesing, but this is all known behaviour and won't change for >know. >
I am sorry I can't agree here. Rugby is very young. It is not used by thousands of users to be reluctant to changes. Simplification is alway a good thing. I am surprised by your statement, as you e.g. agreed to refinementise basic functions. Still some function names/calling conventions are confusing, so why not to change it? so e.g. serve/with [now] http://:9002 serve/with [now] xml-rpc://:9002 could be informative, but serve/with [now] 9002 ; is also nice suggestion or even: serve [now] http://:9002 serve/default [now] is one of other possible conventions, but following is surely confusing: serve/witch [now] tcp://:9002 do get-rugby-service http://localhost:9002 Take it following way - if ppl ask, they are somehow not understanding something = confused. So, please, don't lock ourselves with compatibility issues, especially in very early stages of product development ... -pekr-