World: r3wp

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.

yes, he did - Gab is imo just finishing LNS upon Carl's direction 
....

Well, the BEER one works well enough for me .. though the documentation 
is a little light still.

Yes, I switched to using RebGUI as an experiment, and continued working 
with it as it continues to fufill my requirements.

Ashley is in the business of building database applications so we 
share similar GUI needs :)

Graham , you are  one of those 'wierd' pple in the community as well.


From my understanding, you are  a medical doctor by profession, right?...and 
yet..u seems to be facinated by computing (and rebol).

weird ??

not in the normal sense

Rebol is a tool, and I need a tool to do things.  Such as building 
my EMR/CRM.

Graham - yeksoon is probably not native englisham either - may he 
just means "strange"? :-)

I''m a Renaissance man :)

Anyway, it is really quite impressive how the BEER async stuff works 
with RebGUI

Is there a link for BEER?

no.

But Jaime said he was going to release it at Devcon.

Be prepared and get yourselves a SIT decompressor :(

haha.. he should be able to gzip it

Well, I guess Mac people use SIT as a matter of course.

If you try out the EMR above, select the patient "Mickey Mouse". 
 He has scanned images in his results which can be downloaded while 
looking at consultations.

async is done using call backs as in atcp.  So, if I request a list 
of patient results, my call back function receives the data, and 
redisplays the pertinent list.

Reichart, just sent a message via QTask..that they are having difficulties 
accessing AltMe,


I have copied Pekr's list of questions to QTask so that he can follow 
up on it.

if anyone have questions, it will be good to post it to QTask..if 
you have access.


Reichart will ask the questions after his talk.. (which is the last 
one)....and that will be like morning time for the pple in the States.

Graham - btw - dunno if RebGUI problem or just incorrect definition 
in your code, but try to maximize your window - you will see the 
list of patients (left-bottom corner) resizes incorrectly.