World: r3wp

maybe whineing

My carefully crafted disaster management plan for the Devcon 2005 
included backup videos that I could watch :)

mine included dinking with programs for shootout

Good luck with those .. I'm not sure how much value is in these language 
shootouts

value in personal amusement is sufficent

Tom, howdie

A language shootout on an actual application - such as building a 
p2p chat that passes thru school firewalls - would be more useful.

Hi Aurtur

you in Cali?

oregon

do http://www.ross-gill.com/r/rebcon-map.r

oh, Chris' map kinda showed Cali maybe north a little.

maybe 200 miles to Calif

so what' the news from the conference. What's going on now? Any idea?

breakfast?

no talking

ah Fazoli's

I guess mama always said "Don't tlk when you're eating" :-)

Nobody on AltMe from the Devcon ?
Should be about time for Gregg to start ?

I guess Ladislav has finished talking about BEER now.

Guys - the good thing is, that the plan is to xyz fold Rebol's popularity, 
so next year's Devcon will have to change information strategy and 
imo RT will have to write some announcements or blog articles prior 
to conference, make some short script of - [wait conference-evening 
post articles] kind :-)

BEER is a great framework to use.  They have implented a file transfer 
protocol, authentication, and .. a working LNS profile.

It would be an excellent base upon which to rewrite Altme with file 
sharing.

Except ...

the licensing is GPL :(

It uses a modified version of Romano's ATCP for the async io.

( if Ladislav hasn't started his talk .. I'm in trouble! )

why in trouble? They are not monitoring AltME imo :-) it really does 
not matter, if you release some info, which is gonna be released 
today anyway :-)

is BEER kind of Uniserve?

No.

I have a working CRM done with it.

You can see that it async as you can download files and transfer 
files while still using the GUI.

Uniserve is async in its nature too, no?

http://www.compkarori.com/emr/remr.exe

BEER really requires, as far as I can see, a BEER client.  Whereas 
Uniserve works with anything.

Actually, there is no client/server relationship, it is all peer 
networking.

You have a beer listener, and a beer initiator.

Either can be a listener or an initiator.

The authors were Ladislav, Cyphre and Jaime.

I know it comes from Jaime's group :-) Just trying to figure out, 
what in particular BEER is. I read about BEEP it is based upon, but 
I don't understand its architecture fully. And how does it fit LNS 
- is it a competition to LNS? Or just LNS can be used upon BEER transport 
mechanisms?

.... looking at your app - so you switched to RebGUI already?

Their LNS implementation uses BEER for authentication, encryption, 
and transport.

I started on the GUI a month ago, and with BEER a week or so ago 
to implement the communication protocols.

GPL is weird license though, so mayou you should wait for LNS ....

and use Uniserve instead ...

So, looks like we have three implementations now of LNS,  one from 
Jaime, one from Gabriele, and one from Carl.

It doesn't matter as I am not selling this application .. just personal 
use.

I think not - Gabriele works imo for RT on the contractual basis 
...

... so actually what Gab showed yesterday was official LNS part ...

Well, may be two ... but I presume Carl implemented something before 
he contracted Gabriele and Richard.