AltME groups: search

something like a altme:// protocol loadable within rebol, similar 
to the mySql protocol by Nenad, would be really effective.  reading 
your post from a file browser and saving new posts to it from ANY 
rebol app.    :-)

Component: "REBOL Mezzanine Extensions" 1.2.0 (1-Aug-2004/22:34:12)

Component: "REBOL Internet Protocols" 1.71.0 (4-Nov-2004/21:08:24)
Finger protocol loaded
Whois protocol loaded
Daytime protocol loaded
SMTP protocol loaded
POP protocol loaded
IMAP protocol loaded
HTTP protocol loaded
FTP protocol loaded
NNTP protocol loaded
Component: "Command Shell Access" 1.9.0 (3-Jan-2005/21:08:57)
Component: "System Port" 1.4.0 (1-Aug-2004/18:58:28)

I'm chasing some old scripts from Frank Sievertsen, does anyone have 
the following

[lego.r  math-do.r irc-protocol.r reblog.r] all described here http://www.codeconscious.com/rebol/dialects.html

Jaime: i have functions to do that, you'll find them in the mysql-wrapper.r 
script that comes with mysql-protocol.r

I am having problems connecting to mysql on windows XP. The error 
message I get is "Client does not support authentication protocol". 
I'm using localhost as the host and have granted all priviliges for 
['user''-:-'localhost'']  identified by ''password' .... etc. I'm used 
to linux, and it''s been

(or whatever the Rebol mysql protocol is called)?

I'm going to try it with the mysql-protocol module that I am using 
on my desktop. Just a minute...

But I can't do that for UPDATE !!

So I need to know it the Rebol MySql protocol allow to pass several 
SQL statements in one time.

I have a problem when the connection times out and mysql-protocol.r 
wants to reconnect. It looks like it hangs, but on closer inspection 
with trace/net on just gives an infinite amount of low-level reads 
of length 0 bytes.

Hello, is there anyone working with Rebol Command and Mysql 4.1.x 
? It appears that the authentication protocol has changed and Rebol/Command 
can not connect to MySQL 4.1.x. But it works fine with MySql 4.0.x.

I am not sure about protocol handlers either ... I start to not understand, 
what is rebol - it is not language, nor it is stand-alon platform 
... I want clean design ... Base + SDK is the answer imo ...

Hi Petr, 


Not sure if this is what you are asking about mySQL "Can I update 
particular fields (columns) in table?" but if you want to change 
a value you use SET.  e.g.  in mySQL protocol format


query: rejoin[{update logons set rs='}keyOrder{' where userName = 
'}cgi/userName{'}]
insert db reduce query

I have the new MySQL Version 5 Beta installed on my development Notebook 
(WinXP). I was devoloping a Script acessing a current Version 4.1 
of MySQL without any problems and i thought about continuing dev 
work at home. There i ran into an error saying that the autthetification 
protocol of the client is not supported and i should update my client, 
which is the mysql-protocol from DocKimble, when acessing the local 
version 5 Beta of MySQL. Is this a known problem and does anybody 
knows to work around this?? Does anybody know what changed to authenfication 
that is not supported by the protocol??

This is related, I think, to my notes about VID and MySQL in the 
View section. In a test that we ran in 2004 we were able to load 
1,000,000 rows in under 30 minutes.  We did not investigate further 
but we thought we could improve this by running parallel loads and 
putting it on a real server instead of a laptop.  This volume was 
equal to the annual volume of  the transactions we were interested 
in so would represent a journal of everything that happened to this 
app as a keyed transaction in one year.   


From that 1,000,000 row database, we were able to create an HTML 
report based on some selected criteria in 2.5 seconds.  

All tests done with REBOL View using Doc's mySQL protocol.

I am reopening the issue of mySQL protocol not being able to connect 
to newer >= 4.11 mySQL version database. I decided to consider this 
task as being a proof if the community is, or is not able to effectively 
resort some issues, which clearly show as a show stopper for some 
rebollers (as can be seen on ml). If we are not able to effectively 
resolve this issue, then I have to ask - what actually are we able 
to sort?

Yesterday afternoon I spent investigating Doc's scheme, and here 
are my conclusions:


- The part of code responsible for password communication with the 
server is in the 'scrambler object. The function whish establishes 
connection with server is 'do-handshake


- rebol's mysql protocol seems to distinguish protocol version 9 
and 10, and I was not able to find out, what does it mean on mysql's 
side of things. It also seems to me, there is long-password item 
already in the stack, but dunno if related, it is just osme constant. 
Protocol version 9 and 10 use different hash functions and different 
crypt functions. I really don't know, where does DocKimbel find out 
how to implement those functions, maybe by looking into mySQL source, 
so I downloaded them


- to read more about passwords in mysql, go here - http://dev.mysql.com/doc/refman/5.0/en/password-hashing.html
. Maybe it is not protocol 9 and 10 related, as you may use old password 
scheme even with new databases. The difference is as follows - starting 
from mySQL 4.11, passwords are stored in 41 bytes wide field, whereas 
with older versions, it was 16bytes. New passwords always start with 
* (asterisk) char, to be easily distinguished ...


- how things might work? Mysql sends scrambled password, and Doc's 
scheme stores it in 'crypt-seed variable.  Data is being sent by 
the protocol by 'send-packet function, where for the password part, 
scrambler/scramble function is used, which calls crypt-v10 or crypt-v9, 
according to protocol versions. Those function use hash-v10(9), floor 
and other functions ...


I think that we somehow need to find out, how to compute hash for 
not 16bytes, but for those 41bytes ...

in write-packet, there is part, where he simply sends passwd and 
calls 'scramble on it ... scramble decides upon protocol V9 or V10 
version, and calls crypt-v9 or crypt-v10 accordingly, those two call 
hash-v9 or hash-v10 ....

I was not able to find-out, what just does v9 or V10 protocol mean? 
maybe mySQL protocol version ...

i think so. and a PROTOCOL_41 in a line nearby.

Caps=LONG_FLAG | CONNECT_WITH_DB | COMPRESS | TRANSACTIONS | PROTOCOL_41 
| SECURE_CONNECTION

protocol_41 means a long password?

fix=make it working - we will see - not just with automatic distinguishing 
what password scheme should be used .... good doc, Volker! I searched 
Google yesterday, but did not find the one describing the protocol 
...

hmm, sadly, there is probably bug in protocol read-out directly. 
I thought that salt (seed) is those 8 bytes only. It is so, only 
if old password scheme is used, otherwise another 12 bytes follow. 
But Doc keeps only 8 bytes in crypt-seed word no matter what protocol 
password version is used ...

I may as well extend the protocol, but it may come later :-)

anyway - I regard handshake fixed at least to state, where you can 
obtain full protocol info, according to specs. Of course the handshake 
may be more complicated, but we don't care now, right? ;-)

I fixed the protocol .... just latest bit is needed :-)

without your hint to protocol internals, plust the 2x checksum/secure 
being identical to mysql docs, nothing like that would be possible 
on my side ....

/*

  This file is the net layer API for the MySQL client/server protocol,

  which is a tightly coupled, proprietary protocol owned by MySQL AB.
  Any re-implementations of this protocol must also be under GPL
  unless one has got an license from MySQL AB stating otherwise.
*/

Their protocol can be reimplemented using - http://www.redferni.uklinux.net/mysql/MySQL-Protocol.html

If you do reverse engineering of a protocol in a clean lab environment. 
Then you are protected.

Using means in which you can claim that you didn't use any information 
from the provider to reverse engineer the protocol.

And even if your protocol would have to be GPL, I wonder if anyone 
would found it offensive?

Jaime - with rebol, you even can't to use it, can you? So you use 
mysql-protocol.r, which is let's say GPL. Then you do some app using 
it. You can open-source your app, but you can't open-source one part 
of your app - REBOL itself ... well, I am weak in licensing stuff, 
so I really don't have clear opinion on that issue - just trying 
to use common-sense ...

The protocol of v5 has changed (since v4.x I guess). It needs more 
than just log in the server to make the driver work. I need to update 
the protocol implementation too. I'll try to see if I can make something 
work tomorrow.

http://www.rebol.cz/mysql/mysql-protocol-new.r

Doc, are you sure the low-level protocl changed? The protocol is 
still version 10, which you have covered already. What is more, it 
is strange, as you can work with old passwords, without the change 
to the stack, so I would let it as it is, just let's correctly implement 
the password stuff as first step :-)

I mean - let's find out the way of how to distinguish there is new 
password scheme used for connection. I thought that LONG_FLAG or 
PROTOCOL_411 flags will be set, but they apparently are not set. 
Maybe we could distinguish by long-seed length? If it is still 8, 
then old password scheme should be used, if it is 20, then new password 
scheme is used?

Doc, are you sure your 'docode table is ok? I mean defs/client ....

client [
			long-password		1		; new more secure passwords
			found-rows			2		; Found instead of affected rows
			long-flag			4		; Get all column flags
			connect-with-db		8		; One can specify db on connect
			no-schema			16		; Don't allow db.table.column
			compress			32		; Can use compression protcol
			odbc				64		; Odbc client
			local-files			128		; Can use LOAD DATA LOCAL
			ignore-space		256		; Ignore spaces before '('
			change-user			512		; Support the mysql_change_user()
			interactive			1024	; This is an interactive client
			ssl					2048	; Switch to SSL after handshake
			ignore-sigpipe		4096	; IGNORE sigpipes
			transactions		8196	; Client knows about transactions
		]

While in protocol description, there is:

MySQL uses the following codes:
Capability name	Value	Meaning
LONG_PASSWORD	1	New more secure passwords
FOUND_ROWS	2	Found instead of affected rows
LONG_FLAG	4	Get all column flags
CONNECT_WITH_DB	8	One can specify db on connect
NO_SCHEMA	16	Don't allow database.table.column
COMPRESS	32	Can use compression protocol
ODBC	64	ODBC client
LOCAL_FILES	128	Can use LOAD DATA LOCAL
IGNORE_SPACE	256	Ignore spaces before '('
PROTOCOL_41	512	Support the 4.1 protocol
INTERACTIVE	1024	This is an interactive client
SSL	2048	Switch to SSL after handshake
IGNORE_SIGPIPE	4096	IGNORE sigpipes
TRANSACTIONS	8192	Client knows about transactions
SECURE_CONNECTION	32768	New 4.1 authentication
MULTI_STATEMENTS	65536	Multi-statement support
MULTI_RESULTS	131072	Multi-results

ah, extended the table and it shows:

----- Server ------
Version: 5.0.18-nt
Protocol version: 10
Thread ID: 36
Crypt Seed: iR=xh!fb
Capabilities: [
    long-flag
    connect-with-db
    compress
    protocol-41
    transactions
    secure-connection
]

newer version uploaded - now you can see there is protocol-41 flag, 
as well as secure-connection, according to which you can decide new 
auth. method was used imo ...

so, if you don't confirm there were changes in low-level protocol 
handling (reading, sending, flushing etc. code), then I can adapt 
the code to automatically distinguish for old/new auth scheme and 
respond accordingly. That could be some intermediate version for 
ppl to use ...

MySQL server protocol has changed since 4.1.0 (with a big evolution 
starting from 4.1.1) and is not compatible with the older protocol. 
Strangely, server v5 allow clients to connect with the older (pre-4.1) 
protocol providing the good flags...(that's odd). Need more investigation 
to see if the old driver can still be used reliably with v5.

From 4.1.1, there's a lot of changes in the protocol, mainly a lot 
of new fields.

The protocol number hasn't been incremented, the server and client 
code in libmysql is messy...

yes it is, AFAICT. But it's protocol 4.1.1+, not the old one that 
is implemented in my driver.

I would be able to write it according to specs imo according to above 
protocol, but - I don't understand rebol port model, so :-(

The server has still the support code for all protocol versions. 
That's why the old code is working, but according to the flags, (especially 
protocol_41), it should have rejected your connection. That's why 
I found it odd that your code was working. Anyway, let try to use 
this to make it work with the older code.

I think I know why ... maybe :-) ..... simply put, I don't send protocol_41 
back after the greetings phase ...

latest version: http://www.rebol.cz/mysql/mysql-protocol-new.r

Dock, if you publish a new version of mysql-protocol.r, it's time 
to make the correction of the bug in the init function, the longlong 
conversion and in the data reading initialization.

I have plans for a version 2 of this driver including a full code 
rewritting for much cleaner design, speed improvements, optional 
async API, support more protocol features (like LOAD DATA), implement 
the v5 protocol, improved user API (e.g.: select column in a record 
by field name), etc...

I need one that's integrated into Rebol. Didn't took a look at it. 
Just thought it makes sense to have a protocol like DocKimbel's and 
re-use it with different databases (R-ODBC)

but mysql protocol is not your priority, is it? It simply works now 
:-)

The v3.xx protocol is flawed. The scrambled password is sent to the 
server as a zero terminated string. But the scrambling method, sometimes 
contains a 00 byte. The server then, cuts the password prematuraly 
(error 1043) or if the zero is at the beginning of the string, considers 
that the user didn't provide any password (error 1045).

The new 4.1.1+ protocol fixes that kind of issue by sending the string 
size first (like in Pascal language). The current driver doesn't 
implement the new protocol. This will be the main feature of the 
v2 of the MySQL driver.

I agree, I never use this approach when I design a new protocol. 
It leads to error and it's harder to handle on the receiver side 
because you don't know how much data you're waiting for.

v1.0.3 uploaded. That's my new candidate for 1.0. The connection 
process is now rock solid! I've stressed it with 20,000 connections 
without troubles. The protocol flaw for password is now silently 
handled by the driver by reconnecting to the server.

Apparently MySQL 5 has a datatype that isn't defined in the protocol, 
adding this line seems to work just fine:

defs/types 246 decimal

I'm getting the Error 1043 Bad Handshake problem accessing My-SQL 
5.0.18 on Windows/XP using mysql-protocol.r via  localhost: that 
Alain Goyé reported on the mailing list:

>> db: open mysql://root:?@localhost/fundamentals
Password: *********
connecting to: localhost
>> insert db "SELECT * FROM books"
** User Error: ERROR 1043 : Bad handshake
** Near: insert db "SELECT * FROM books"

It works fine from another machine over the LAN.

I've just realised that I' have old_passwords set on and am using 
the latest version of Mysql-protocol.r :-(

I solved the problem by installing the 0.99 version of mysql-protocol.r. 
It was quicker than trying to get XAMPP to accept a MySQL revised 
configuration file.

Tried creating a user using that tool under WinXP and OSX, then I 
tried connecting with mysql-protocol.r => no problem...

I think the client is confused about that. The error log for it says 
that old passwords are not supported for 5.0. I initially tried to 
turn old passwords on, because I didn't think mysql-protocol.r supported 
newer ones.

copying old 3.x files in v5 server works but results in a big mess 
and unstable behaviour
 <--- is that because of MySQL or mysql-protocol.r?

Thank you. With the old protocol I would sometimes get  an error 
 (and exit from the program) when I inserted into a closed port. 
I will give these a shot.

do %mysql-protocol.r
do %mysql-client.r
mysql

They use Debian. I have Fedora at home. What would I like to ask 
is - where to put rebol interpreter on Debian? Where to put things 
like user.r or mysql-protocol.r or whatever other script I produce 
to them? The path is almost always trouble for me. I e.g. start console 
and I have to define set-net once again, as it does not use my user.r 
settings etc. Any insights?

(local machine)

and it returns:

make object! [
    server-software: none
    server-name: none
    gateway-interface: none
    server-protocol: none
    server-port: none
    request-method: none
    path-info: none
    path-translated: none
    script-name: none
    query-string: none
    remote-host: none
    remote-addr: none
    auth-type: none
    remote-user: none
    remote-ident: none
    Content-Type: none
    content-length: none
    other-headers: []
]

With Apache 2.x (normal CGI), we have: make object! [ 
	server-software: "Apache/2.0.54 (Fedora)" 
	server-name: "localhost" 
	gateway-interface: "CGI/1.1" 
	server-protocol: "HTTP/1.1" 
	server-port: "80" 
	request-method: "GET" 
	path-info: "/sample01.rhtml" 
	path-translated: "/var/www/html/sample01.rhtml" 
	script-name: "/cgi-bin/magic.cgi" 
	query-string: "" 
	remote-host: none 
	remote-addr: "127.0.0.1" 
	auth-type: none 
	remote-user: none 
	remote-ident: none 
	Content-Type: none 
	content-length: none 
	other-headers: [
		"HTTP_HOST" "localhost" 

  "HTTP_USER_AGENT" {Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) 
  Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6} 

  "HTTP_ACCEPT" {text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5} 
		"HTTP_ACCEPT_LANGUAGE" "en-us,en;q=0.5" 
		"HTTP_ACCEPT_ENCODING" "gzip,deflate" 
		"HTTP_ACCEPT_CHARSET" "ISO-8859-1,utf-8;q=0.7,*;q=0.7" 
		"HTTP_KEEP_ALIVE" "300" 
		"HTTP_CONNECTION" "keep-alive" 
		"HTTP_COOKIE" "PHPSESSID=7f84fd7766f23e1462fed550ecbbfda4"
	] 
]

this is an article I wrote in 2003 hacking the http protocol to do 
this too http://www.compkarori.com/vanilla/display/HTTP+file+uploading

Winding down: Apache CGI with RSP is pretty good these days. If you 
combine:
- module management
- logging
- error handling
- session management
- database protocol (mysql://)
- CGI params handling

you can "just work".

I know I can use mysql-protocol to access mysql directly but that 
is not hat I mean as sometimes that is not possible/allowed by some 
isp's.

Are this functions kind of standard? Then we could start with some 
"protocol" implementing the functionallity.

I know we discussed writing a SOAP:// protocol years and years ago 
on the mailing list ... but that never got done.

I made a little change to the http protocol to send SOAP messages 
.. so that I could access the National Library of Medicine's RxNorm 
API.

The web and soap/http are in a sense REST applications (REST is just 
WS over HTTP) though both use a limited subset of REST arguments 
and have to work around as such.


The web is limited (by the HTML spec) to the verbs 'get and 'post, 
and post content types of 'application/x-www-form-urlencoded (default) 
or 'multipart/form-data (used to upload files).  For the most part, 
the web is RESTful as we usually only want to 'get resources.  However, 
other operations typically violate REST principles, as all other 
resource actions (create, update, delete) have to squeeze through 
the get/post/url-encode/multipart pipe.  The Rebol HTTP protocol 
as standard is designed to mimic this and requires patching to move 
beyond get/post/url-endode (even for multipart)


SOAP as I understand it, when using HTTP only uses 'post - the post 
content contains the actual request.  Where it varies from the web 
(and Rebol HTTP) is the need for the 'text/xml content type.


REST itself is limited only by HTTP.  It uses theoretically limitless 
HTTP (v1.1) verbs (though most common patterns use 'get, 'put, 'post 
and 'delete).  It uses any encoding.  It uses HTTP headers as parameters 
(eg. the 'Accept header specifies the desired return type).  Therefore, 
any HTTP protocol designed for REST will accomodate SOAP requests.

Given some xml like this which is a list of documents http://code.google.com/apis/documents/docs/2.0/developers_guide_protocol.html#ListDocs

how would your parser extract the <gd:resourceid> and text associated 
with these tags?

The semantic model of REBOL protocol schemes, implemented with the 
port! type, would fix well with the semantic model of SAX pull. SAX 
pull generates the same SAX events, except they are not propagated 
through callbacks - instead they are returned from function calls. 
SAX pull is sort of like an generator (in the Icon or Python sense) 
of SAX events. That is very similar in model to the behavior of command 
ports (like database ports).

Just wanted to say, that I needed async postge SQL protocol, so I 
used the Nenad's non-async version located here: http://rebol.softinnov.org/pgsql/
and made async my own version, which is available here: http://box.lebeda.ws/~hmm/rebol/a-pgsql.r

I've been using  pgsql-protocol (r090)  to store HTML reports into 
the DB. 


It can write a large compressed string into a text column ok. Trying 
to read the data back causes the program to hang. The length of the 
stored string returns 182514 chars. (In psql: SELECT length(html) 
FROM reports....)

Test Code;

sql: {SELECT html FROM reports.html_reports WHERE ticket = '2007-756-fcw'}
insert db-port sql
html: first db-port
.... rest of test program never gets executed.

Does anyone know if this a known behaviour? Thanks

For information, if I select any other column, the program runs as 
expected. The data is these columns is a lot smaller in length.

There is a native non-odbc client library for ms sql that is fast. 
There is also a TCP line protocol to access it.

By the way, ODBC and OLEDB are the native access methods of MS SQL 
Server - they are not an add-on layer. The tcp line protocol is the 
same protocol that the client libraries use. I think there is a few 
open source libraries that support the tcp connections (such as FreeTDS), 
though they may not be very current. You might be able to look at 
their code and docs to figure out the protocol.

I am trying PGSQL with Doc's protocol and getting 'open pgsql'  error 
"** Script Error: find expected series argument of type: series object 
port bitse
t

** Near: fast-query: either args: find port/target"     This is Postgres 
9.0 recently downloaded.   Anyone having success with it?

This is the new version to try: http://softinnov.org/tmp/pgsql-protocol-091.r

The error message seems to be the problem ... the table is CREATEd 
and is usable from new rebol sessions which load the protocol fresh.

Thanks Doc.  I can work around that TABLE message using the pgAdmin. 
 The Send-SQL and /FLAT protocol updates work exactly the same as 
on MySQL for me.

The cause of the error above is a communication protocol change, 
the driver was made for 7.x. It would need a good upgrade.

You mean, without computer being on ? Can't be done, due to Skype's 
proprietary protocol.

Not using Skype protocol.

Perhaps better than Skype because it claims "No supernodes", but 
you still need a computer as it uses a proprietary protocol.

Thanks, I'll take a look at it. (Marco's sql-protocol.r is also a 
good read).

Ashley, sql-protocol generates the code used to extract and join 
the data is grouped in 2 functions :
- make-do-select
- make-do-loop

They receive the column list, the table list (a block of table/alias 
pair), the where code to apply and the database (the port).


If you provide these parameters and change the code to invoke RebDB 
fuction to get the data, you will have a basic join implementation 
for RebDB. You can use it and extend it for RebDB, if you want, I 
will be happy if you do so.

sql-protocol don't need these heavy use of 'compose, 'join, 'reduce 
 if you use the dialect. Something like this work :
   var1: "Marco" 
   insert my-db [select * from my-table where name = var1]
   my-result: copy my-db

Another example to ilustrate this :

   insert my-db [select * from my-table where name like rejoin ["*" 
   var1 "*"]]


This is only if you use the dialect to query the database. If you 
use the standard SQL string, you need to compose the query.

Anyone had any experience with SQLite (http://www.sqlite.org/), especially 
in conjunction with REBOL? What are the limitations of sqlite3-protocol.r 
(http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=sqlite3-protocol.r), 
if any?

I'm interested to see how folks have dealt with issues such as:


 1) Support for datatypes other than TEXT, INTEGER, NUMBER and BLOB?

 2) All tables in one DB, or one table per DB to improve concurrency?

 3) Multi-user access across a network, given this statement from 
 the SQLite website:


SQLite uses reader/writer locks to control access to the database. 
(Under Win95/98/ME which lacks support for reader/writer locks, a 
probabilistic simulation is used instead.) But use caution: this 
locking mechanism might not work correctly if the database file is 
kept on an NFS filesystem. This is because fcntl() file locking is 
broken on many NFS implementations. You should avoid putting SQLite 
database files on NFS if multiple processes might try to access the 
file at the same time. On Windows, Microsoft's documentation says 
that locking may not work under FAT filesystems if you are not running 
the Share.exe daemon. People who have a lot of experience with Windows 
tell me that file locking of network files is very buggy and is not 
dependable. If what they say is true, sharing an SQLite database 
between two or more Windows machines might cause unexpected problems.

[uniserve] Async Protocol FastCGI loaded
[uniserve] Starting task-master...

## Error in [uniserve] : Cannot open server task-master on port 9799 
!
[uniserve] Starting HTTPd...
## Error in [uniserve] : Cannot open server HTTPd on port 80 !

is all I get...

is FastCGI.r usable separately as a free fastcgi protocol for REBOL, 
or does it work only in terms of Cheyenne?

Pekr: The protocol is not specific to Cheyenne, but you'll have to 
"extract" it from the module to be able to reuse it. But, we're talking 
about a FastCGI CLIENT implementation, and what you have in mind, 
I guess, is a SERVER implementation (like in /Command)...

No, it's a client implementation of my own (/Command implements a 
server-side FastCGI protocol)

Both versions act the same. Win XP Home. No crash.log file found. 
 This is what loads:

[uniserve] Async Protocol FastCGI loaded
[uniserve] Starting task-master...
[uniserve] Starting HTTPd...

but yes, tools for sharing would be fine. We should look at tools 
line MS Collaboration server or Lotus Sametime - kind of multi-icq 
app - you drag and drop users there, you can make screenshots, post 
them directly to channel, you can draw and post it, you can share 
your app to other (probably using RMD (remote desktop) protocol in 
Windows)