AltME groups: search

This looks pretty promising. The sync4j server seems to be the thing 
we need to get access to the phone. And it can be expanded with connectors 
so others can use the server as a proxy. There exists an email connector.

REBOL [
	Title: "Local Index" 
	Type: 'index 
	dynamic: true 
	plugin-pane: 0.5
]

title "Local Files"
app 0.3

group "A" effect [multiply green] 
			 
group "B" icon %action.png

action "a\gitarre"    do [explore %/f/gitarre/]
action "a\view-root" do [explore view-root]
action "a\hamster"   do [call "H:\prog\Hamster\Hamster.exe"]

action "b\Internet" do [
	call "H:\Programme\offline-proxy-mm3\MM3-WebAssistant.bat"
	call "C:\Programme\discountsurfer\discountsurfer.exe"
	call "H:\Programme\Mozilla\Firefox\firefox.exe"
	call "C:\Programme\Opera75\Opera.exe"
] 


action "b\Firefox" do [	call "H:\Programme\Mozilla\Firefox\firefox.exe"] 
icon %web-surf-action.png

action "c\desktop"   do [editor view-root/desktop.r] 
action "c\imap"      do [editor %imap-handler.r] 

file "Info" %info.txt
file "T\Test" %test1.r 
file "T\Test2" %test2.r 
file "T\Test" %test3.r

; this is composed ----
file (form now/date) %dummy.r

action "Click me" #clickme do [
            alert "hi"

            [Text "This will be displayed within the desktop" [alert "ho"]]
          ]

action "Click me 2" #clickme2 do [
            alert "hi"
			; no return value, so nothing displayed in the desktop
          ]

action "PRINT" do [print "^/^/----------------------^/^/^/"]
action "prin somethin" do ["yea"]
file "t\Test" %dummy.r

; this will draw the plugin
app-draw [face /local cl-size][
   cl-size: to pair! reduce [face/size/x 50]
	face/pane: layout/offset[
		at 0x0 
	   text "00:00:00" cl-size center 255.155.40 with [
   		font: [size: 24]
	   	rate: 1
		   user-data: none
   		feel: make feel [
	   		engage: func [face action event i] [
		   		if user-data <> now/time [
			   		i: form user-data: now/time
				   	if 7 > length? i [append i ":00"]
					   face/text: i
   					show face
	   			]
		   	]
      	]
      ]
      text "TEST" 
		button "hi" [alert "you!"] 
   	button "CLOSE" [unview/all] 
	] 0x0 face/size 
]

; if you need to redraw after a resize, not yet used
app-resize [new-size][]

Doc would be nice to see your NTLM module applied to enable other 
applications to be proxyaware such as acting on a layer as a port 
fowarder could possibly allow ALTME to have MS proxy capabilities?

I already have a NTLM proxy built on UniServe that could do the job, 
but for AltME, to be able to pass a MS Proxy, it has to first, use 
HTTP as transport layer (IIRC it's not using HTTP currently ?).

I don't think that MS Proxy is limited to HTTP traffic.

ans proxy settings are useless

Proxy settings has a low priority in the AltME wishes list, mainly 
because it hasn't been important enough to anyone to add a brief 
description of what is wanted.

I don't think we should have proxy settings on the list.

the reason is that the proxy problem is with some proxy servers and 
occurs with all rebol applications.  In particular, I can point to 
squid.

I checked this by using a proxy that worked fine with rebol. I then 
switched to squid, and it failed.

So is it possible to phrase the requirement better than "proxy"?

Is the requirement for an AltME client to access an AltME server 
from behind a firewall or proxy server?

At least that's one possible interpretation of "proxy" ruled out.

Anton, if the proxy only allows http packets .. then there is nothing 
that RT can do about this.

for Info: To use Altme behind a proxy is use 2 linked apps: "Proxifier" 
to force Altme to use a proxy and "HTTP Tunnel" to bypass the local 
restrictions of the company's proxy.

AltMe does work via proxy, no? The problem is world lookup feautre, 
which requires certain port to be opened on FW IIRC.

no as far i know (i've done many test) Altme dosn't work behind a 
proxy

i precise, a proxy which use user/pass authentification

hmm, I am behind proxy right now ... well, no authentication though 
....

How does AltME launch web browser? I have my browser defaulted to 
FF, but it always starts IE. Not that it would be much of a problem, 
but IE proxy setting is set by our Active Directory rule with each 
log-in, so at home I have to constantly change the proxy setting 
each time I get home, in order to be able to start links directly 
from AltME ....

Ports: Hi, I want to setup AltME in a way that it connects to a local 
port-forwarding proxy which than tunnels the connections.


What local ports does AltME use? And what are the remote IPs / Ports 
I need to use?

I tried to use a SOCKS proxy for dynamic tunneling but AltME doesn't 
seem to have SOCKS support done right or at all.

I try again. Someone mentioned he got AltME run through a proxy. 
I still failed with support from programs like Proxifier etc. But 
please note that I tunnel all the traffic through SSH as well.

Any chance of getting an ALTME version that support MS proxy authentication. 
 I know that DOC Kimbel has a proxy authentication that works on 
large enterprise environments.  If it can work, I will go to EDS 
and see if they would support purchasing ALTME as a collaboration 
solution.

I experienced proxy problem too last week, when I tried to connect 
at meeting room at our dislocated company location. I needed go via 
the proxy. Dunno if AltME supports proxy at all?

It supposed to support socks proxy but MS proxy requires either Kerberos 
authentication (the current standard) or NT LAN Manager authentication. 
 Doc's implementation does the NT LAN Man authentication.  Which 
if ALTME does that it means support for older windows systems as 
well since older ones don't support kerberos.

I think, that AltME would greatly benefit from DevBase model. DevBase 
is live demostration of community collaborative work. If AltME client 
(not necessarily server) sources would be uploaded, we could see 
good bunch of small refinements, fixed proxy, etc.

which means that again I will need another daemon to act as the proxy 
to the SDB.

Do you think it would make sense to implement few AltME enhancements, 
which would not alter its messaging layer, but could help to make 
our lifes easier? Some few months ago I contacted Carl, and he was 
willing to post particular code sections for related areas. I read 
also some 2005 list, and picking from (apparently easy to fix) bugs/enhancements:

- DeRED - mark everything read
- fix URL display bug
- fix proxy
- fix msg loss during reconnect .... (might be more complex)


I just don't know, if it is good to bother Carl with those issues 
right now, when R3 is heading towards beta and we need to concentrate 
on it ...

I also always wondered, why proxy does not work, if we have it available 
:-) (but that's different topic)

I have a slightly modified help, that does not evaluate functions 
in objects and ports and that also dumps ports like objects.
>> a: open http://www.rebol.com
connecting to: www.rebol.com
>> help a
A is a port of value:
   scheme          word!     HTTP
   host            string!   "www.rebol.com"
   port-id         integer!  80
   user            none!     none
   pass            none!     none
   target          none!     none
   path            none!     none
   proxy           object!   [host port-id user pass type bypass]
   access          none!     none
   allow           none!     none
   buffer-size     none!     none
   limit           none!     none

   handler         object!   [port-flags open-check close-check write-check 
   ini...
   status          word!     file
   size            integer!  0
   date            date!     6-Nov-2006/21:26:44
   url             string!   "http://www.rebol.com/"

   sub-port        port!     make port! [ scheme: 'tcp host: "www.rebol.com" 
   po...
   locals          object!   [list headers querying]

   state           object!   [flags misc tail num with custom index 
   func fpos i...
   timeout         integer!  30
   local-ip        none!     none
   local-service   none!     none
   remote-service  none!     none
   last-remote-service none! none
   direction       none!     none
   key             none!     none
   strength        none!     none
   algorithm       none!     none
   block-chaining  none!     none
   init-vector     none!     none
   padding         none!     none
   async-modes     none!     none
   remote-ip       none!     none
   local-port      none!     none
   remote-port     none!     none
   backlog         none!     none
   device          none!     none
   speed           none!     none
   data-bits       none!     none
   parity          none!     none
   stop-bits       none!     none
   rts-cts         logic!    true
   user-data       none!     none
   awake           none!     none

Is there interest in including in the new release?

I tried Carl's site monitor - Gismo, but it converts sites to tcp 
ports, instead of staying with http ... how can I easily add proxy 
support to manually constructed tcp port? I do remember some tricks 
with subport where actually port is, but can't make it work easily 
...

looking at sterling's proxy script, I somehow can't understand that 
sub-port concept :-) Looking at rebol core manual, it does not make 
my life any easier :-) Although I can understand the concept of root-protocol 
and how to establish new scheme, it does not help with understanding 
of lower level issues ...

simply put - scheme model is not so complicated, you can even rather 
easily go and use tpc and udp ... but unless you need something like 
a proxy support ....

you mean automatic proxy detection?

Do you mean this ?:

Terry's machine ---- ( internet ) ---> proxy machine ---> target 
machine
where the target machine is the ip you want.

I am supposing a remote machine has connected to a service of yours, 
and you want to know if you can inspect the port in such a way as 
to obtain the ip of the remote machine, even if it is behind a proxy.

proxy isn't correct

My script checks for proxy ,and fetches the forwarded address.

Some of these scripts only give you the address of the proxy.

(if you are not using proxy)

I further investigated the problem. First I use three different boxes, 
that use the same iteration function. The iteration function uses 
different proxy faces. So, each box uses its own proxy face.

- currently when you install, it seems to work correctly, untill 
you choose to uninstall. You typically go to control-panel/install-uninstall 
icon, you find Rebol and choose to unistall. That is great, but that 
entry seems to be shared between the accounts. So - I tried installing 
for two accounts and IIRC the entry vanished and in fact second user 
could object, that he can't regurally uninstall Rebol

- currently View contain rather nasty bug, which does NOT allow it 
to be run without the installation at all. Try to uninstall Rebol 
and then try running it rebol.exe -i your-sript.r, it will try to 
launch desktop and what is more it will try to connect to internet 
and if you are behind proxy, god save you, because Rebol blocks and 
you can't shut it down even using ctrl alt del combination, and that 
is REALLY ANNOYING and knowing myself, if I would be newcomer and 
would like to try Rebol, it would go into trash just because of that 
...

So - to be constructive - I reported error into RAMBO and it was 
market as critical, although I am not sure if it will be fixed, mostly 
ppl will not try to run rebol app directly, or they will simply install 
it, but currently View 1.3 is UNUSABLE in environment, where you 
want to use it over network, starting in login script, and do some 
maintanance to your machines - because desktop will pop-up. I also 
reported how Rebol should check for proxy settings, where those are 
placed in Registry, as it seems to me current method is weak ...

The ability to evaluate code examples in the word browser was done 
without inserting a "proxy" print statement, or probe, or others, 
and the code examples were not updated either. It's a bad solution 
for now; just a first step.

Yes, that might work Volker. The first thing to do is make all the 
code examples consistent and define the standard for how to write 
them, so we know which "output channels" we need to handle. e.g. 
Carl put in a proxy for the VIEW function, so examples that use it 
would do a VIEW/NEW automatically.

If the band is bound to a proxy, maybe not.

yes, they should, but then rebol's ability to read system proxy settings 
should be fixed - I know what I talk about ;-)

Maybe a requester. "Testing proxy" and choice for seconds

well, even if IE is used by 85% PCs on average, plugin can be used 
by some 60 or so percent, who are lucky not being behind proxy. Rebol 
proxy support detection sucks big time ...

I add the probe do-events and here is the result:
probe do-events

make port! [
    scheme: 'event
    host: none
    port-id: none
    user: none
    pass: none
    target: "events"
    path: none
    proxy: none
    access: none
    allow: none
    buffer-size: none
    limit: none
    handler: none
    status: none
    size: none
    date: none
    url: none
    sub-port: none
    locals: none
    state: make object! [
        flags: 4719107
        misc: none
        tail: 0
        num: 1
        with: "^/"
        custom: none
        index: 0
        func: 12
        fpos: 0
        inBuffer: none
        outBuffer: none
    ]
    timeout: none
    local-ip: none
    local-service: none
    remote-service: none
    last-remote-service: none
    direction: none
    key: none
    strength: none
    algorithm: none
    block-chaining: none
    init-vector: none
    padding: none
    async-modes: none
    remote-ip: none
    local-port: none
    remote-port: none
    backlog: none
    device: none
    speed: none
    data-bits: none
    parity: none
    stop-bits: none
    rts-cts: true
    user-data: none
    awake: func [port][wake-event port]
]

REBOL/services - architecture developed by RT themselves, which will 
be part of every REBOL release, to standardise. You can find it via 
rebol.net IIRC. There are some docs, examples. It is not fully finished, 
it does not work if you are behind the proxy, and is not properly 
async, hence ppl work for R3 (which is async by default). Very strong 
concept, and once R3 is out, we will ruin other languages world via 
simplicity. You should also learn more about dialects, what they 
are, how those could be used, etc.

it is installing non aproved applications that is the issue, and 
the need for a proxy config? perhaps that is covered.  I may just 
install it I suppose.

Maybe you could write a simple proxy for system/ports/input, catch 
CTRL-V then redirect clipboard:// content to console?

Doc, or anyone, do you know how to write a proxy for system/ports/input 
?

I would try to wrap a custom port wiring all methods to the console 
port then I would replace system/ports/input with that new one and 
see if the "proxy" port works. If it works, then you can intercept 
the incoming events and add your own handlers. But that's only theory, 
as much other low-level parts of REBOL, it's not documented, so I'm 
not sure it would work.

(You are right about terminal signalling, but of course this is not 
the only thing this proxy port is useful for.)

Does anyone have experience with NetApp NetCache proxies? http://www.netapp.com/products/netcache/

My REBOL solution calling services over HTTPS works ok with the Squid 
proxy, but not with NetCache. Any ideas?

to try the current version, set your browsers http proxy to

Proxy: bionix.cs.uoregon.edu
Port:  3776

untested

an echo proxy   .... 3776 is "EC0" in hex

for http proxy lists ...http://www.samair.ru/proxy/

page: read http://www.samair.ru/proxy/proxy-20.htm

== {<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

All the arguments are there (I checked with a reb-proxy, the page 
itself is very ugly)

NTLM support library for REBOL v1.0.3 released. Download here : http://softinnov.org/rebol/ntlm.shtml


If you've had issue using this library before with a MS (NTLM) proxy, 
please give it a new try. It fixes a major issue with NTLM proxy 
and has been updated to work with 2.7.6.

still missing --noconnect, unless proxy code is fixed ....

hmm, can't connect, have to check my proxy settings :-(

hmm, curious if you guys will make it to work, as key-speach by Carl 
is friday am, so I will have to take vacation to stay at home to 
watch it :-) (as when at work, we are behind the firewall and I don't 
expect it to work, if it does not support proxy and default 80 port 
....)

Maxim  - damned proxy support!

(proxy)

and the main web page is really big piece of s..t... I will update 
my proxy to cound number of MB which I have to download to see simple 
webpage with no effects

and the one reason we continue using rebol is because we are of the 
type of people who WILL download an RFC and fix the http, ftp, proxy, 
xml, (whatever) protocol ourselves.

And use cgi only as proxy.

If I have a proxy server made in Uniserve, what is the best way to 
join it with Cheyenne?

And where I should add protocol? If I used to start the proxy using:

uniserve/boot/with/no-loop [services [proxy-http] protocols [http]]

You can run an HTTP proxy server on port 80 and run multiple instances 
of Cheyenne or other HTTP servers on other ports. The proxy server 
can route traffic to the appropriate Cheyenne instance based on configuration. 
nginx is lightweight and fast, and I have used it for this purpose, 
although my experience with it is limited. You can find more information 
here: http://en.wikipedia.org/wiki/Reverse_proxy

as a proxy

Proxy: it can be done but requires a little more work, like building 
your own mod-something and implementing an async client protocol 
in Uniserve (unless you want to use the built-in HTTP async client 
protocol).

You need a proxy.

Robert, one thing you can do for sure is reverse proxy rsp to cheyenne 
and serve static from lighthttpd 8)

I'm using Cheyenne with Apache using the reverse proxy. Don't know 
it it's possible with lighthttpd. Let us know:)

Cheyenne's RSP with other web server : no. The reverse proxy technique 
works well.

reverse proxy on apache2 with apache on one ip and cheyenne on another 
ip, put something like this in your virtualhost config:
	ProxyPass /00/core/ http://192.168.0.110/media/
	ProxyPassReverse /00/core/ /media/
	ProxyPassReverseCookiePath /media /00/core
of course you'll have different ip and path

this one is a little different and a bit more expensive on resources, 
if a request doesn't exist (no file match, no folder match) proxy 
reverse to cheyenne:
	DirectoryIndex default.html index.html
	RewriteEngine on
	RewriteCond /Volumes/data/web%{REQUEST_FILENAME} !-f
	RewriteCond /Volumes/data/web%{REQUEST_FILENAME} !-d
	RewriteRule ^(.*)$ http://cheyenne.com$1 [P]

one advantage of proxy reversing is you can gzip with apache, rebol 
doesn't do that natively

Do you guys advise running cheyenne behind reverse proxy or direcly 
on web in general? (if I would use reverse proxv I would try nginx)

Proxy : I run all my Cheyenne servers directly on web. Adding a reverse 
proxy frontend like nginx might be usefull for heavy loaded sites 
(millions hits/day) or when you need load banlancing and fault tolerance.

Before setting-up the reverse-proxy config so that I can use cheyenne 
with all RSP features I have some questions:


1. Session handling: I understand that sessions can now be used via 
cookie, URL-parameter or POST data. How do I select which method 
to use? Can I start with Cookies and if this fails (can this be detected?) 
fall back to the other methods?

Is HTTPS supported? If not, can I make use of lighttpd HTTPS support 
with this revers-proxy setup?

Cheyenne doesn't have built-in SSL support (Carl never enabled server-side 
SSL for ssl:// scheme). The "lighter" way to support that is to use 
a specific wrapper like stunnel. Lighttpd in reverse-proxy is ok 
too, but maybe overkill.

I can see that cheyenne processes this page via the revers-proxy 
setup but nothing is delivered. The browsers hangs and shows the 
progress bar.

I'm now using Cheyenne as reverse proxy with lighttpd. Works great. 
All RSP requests are forwarded to Cheyenne.

Thinking about web-app appliances. Not sure if this idea alreaday 
exists but IMO a good thing to think about.


If I have a RSP based web-app (for example my super-cool-all-you-need-shooping-cart 
system) that I would like to sell it would be nice to bundle cheyenne 
and all the RSP stuff into one package. The user just installs it, 
sets up a simple reverse-proxy and has everything up & running.

Pekr a little help for the problem when a existing apache/lamp website 
needs additonal web-app that you would want to write using cheyene 
would be to use Apache's mod_proxy to map just some path to cheyenne 
 > ProxyPass > ProxyPassReverse  -- http://httpd.apache.org/docs/2.0/mod/mod_proxy.html

Having a Cheyenne running locally using a browser window to display 
VID dialect looks like very doable. I think that even 'move events 
would work fast enough. That would solve a lot of current View/VID 
issues while providing a cross-platform GUI. Add a proxy service 
to Cheyenne, and you got a nice RIA platform with online/offline 
working capabilities.  Anyone rich enough here to sponsor such project? 
:-)

I use Cheyenne as a reverse proxy. I think in this setup the HTTPS 
things is handled by the primary web-server, communication to the 
revers proxy is non encrypted and hence this setup should make it 
possible to use Cheyenne's RSP with HTTPS. Not elegant but it should 
do the job.

The last entry was probably the cause of some of the rare "RSP freezing" 
issues. I've stumbled upon it recently while making a demo of one 
of our web-based products using IE7 through a proxy.  By default, 
IE7 switches to HTTP1.0 when connecting to a proxy causing the extra 
CRLF bytes after POST data to appear.

yes, dialect based solution would be very interesting ... I was thinking 
about dialects a little too (not concrete yet) ... currently my testing 
engine is made so that it uses a proxy and it records your what you 
do via browser and then it can repeat the same and comparte the output 
(it already figures out that it needs to set different cookie and 
some basic stuff to login for example , and I have idea to make it 
scriptable for other dynamic data but I haven't come that far yet 
) . It also doesn't do any smart comparisson of the outputs, but 
more of a report for human to view for now

The recording proxy can be a very efficient approach for non-regression 
testing.

Mostly nothing. Cheyenne is working as a reverse proxy and just servers 
an RSP file.

hopefully proxy will be automatically detected on Windows :-)