World: r3wp

But if that anything is not that popular/needed, like javascript/flash, 
it canbe not instlled too.

Does the plugin have to adhere to safety standards higher than any 
other plugin language?

So there are two basic needs: confirmation of  trust (signing) and 
program limits.

G: that is a good question.

We should be at least as high.

Note that we also now sign the DLL, to prevent the hack "modify the 
security requestor text".

IMHO we are the new guys, and the doors are locked more easily.

The DLL uses authenticode verification.

Ok, so it is 10:50 here in Paris... and I must go.  But I ask for 
your help so we can make the plugin complete, and as soon as possible.

Carl, I hope, you have a good vacation! Paris is nice. I were there 
last week.

Thanks for logging in and making that committment, and writing in 
english!

In my mind, and as I've stated, I think we must consider a 2.6.3 
release as well -- for some bugs that are critical.

IMHO that would work. makesure the script is by me, and that icant 
look in your private stuff except i am extremely nasty.

Yes, Paris is a very nice town.

2.6.* is still a good language :)

I would like to move here to complete R3.0 --- But, Cindy does not 
seem that excited about doing so.

Yes, thanks.

So, must go now.  I will try to check in tomorrow too.  This timezone 
is easier for me to do so.

cu :)

Complete 3.0? :-) Is 3.0 so close to alpha release or so? :-)

regarding plug-in, my concern is just one - proxy - without it it 
will be no-go for ppl behind the proxy. My understanding is, get-net-info 
needs update ...

Yes. Confirmed. Josh is working on better way to obtain the proxy 
information, according to MS methods.

Sorry, although 3.0 is highest priority, we are "multiplexing-in" 
a few other tasks.

Just so you know for sure: we do plan to make a 2.6.3 (1.3.3) update 
to fix various R2 bugs, including a range of OSX related issues.

Gabriele is the main contact regarding the R2 priorities.  So, you 
must talk to him if there is a critical bug that you need scheduled 
for fixing.

It certainly makes sense to complete those things that can be readily 
done ...given that R3 may be months away

The desktop is nearly dead anyway.

Google and Microsoft are battling for ownership of the web space.

Rebol has a chance now that paradigms are shifting into general acceptance.

that the desktop is being superceded by internet applications.

But we need to be there in less than half pie fashion ...

We don't want to be crippled by lack of SSL and other show stoppers

Hi.  location   not work in Firefox  1.5  .  try it  code :    do-browser 
 "location='http://rebol.com'"

Micha: Try this: do-browser "location.href='http://rebol.com'"

Plugin "completion" project: As Carl said, we are going to take the 
steps necessary to make a R2 "complete" plugin.

Based on your feedback, I've divided this project into three areas:
	1. Stability (no bugs, Win2k support, etc.)
	2. Security (signing, program limits, etc.)
	3. Proxy (correct proxy detection)


Is that accurate? Do you think that after addressing those three 
areas, the plugin would be "complete"? If not, what other areas do 
you think we need?

1. IE 
2. Firefox
3. Safari

Opera

But yes, Josh, it seems like correct order. I give my vote to proxy. 
Dunno how many folks work in companies behind the proxy, but because 
there is not user.r by default, nor there is some abilitiy to launch 
desktop, the plug-in should do as much as possible, in regards to 
correctly detect proxy ...

Josh, that looks good to me.  Proxy would be good.

Josh, I believe the Proxy support is really needed and obviously 
that could be used in REBOL3 for universal use.  I hope you implement 
both kerberos and NT LM Authentication.  I know that Doc Kimbell 
already has a tested Proxy implementation using the NT LM Authentication 
on his website.

If I recall the Kerberos is the default authentication on newer MS 
operating systems and NTLM is the older legacy authentication method 
that should be incorporated to support a more diverse environment 
where Win9x  and NT 3.5-40 machines might be in use.

I know in my environment where we work with multiple customers with 
thousands of workstations in interconnected networks and extranets 
we definately need the proxy support.  We have so much proxy authentication 
going on between internal networks due to acquisitions where segmentation 
and security are still sensitive concerns.

Proxy: I've broken this sub-project down into two areas:

 1. Detection (auto-proxy, manual proxy, etc.) -- obtaining the correct 
 proxy server address for a given URL.

 2. Authentication (NTLM, Kerberos, etc.) -- authenticating with the 
 proxy server

Are there other areas you see related to proxy support?

not known to me .... but I know only a little about it ....

For NTLM authentication, isn't there some OS API to do that ?

I can't imagine that each program using Internet has it's own NTLM/Kerberos 
authentication scheme!!

Yes, I'm looking into both OS API and native methods.....

Question: On these systems that need full proxy support, are you 
running the latest OS? (i.e. WinXP SP1+, Win2k3, or WIn2k SP3+)? 
If so, there is OS support in those systems that may make this significantly 
simpler...

as for me, yes, no W9x machines ...

Am I correct in assuming that the majority of these proxy scenarios 
are just downloading HTTP/FTP files? Is there a case where you need 
upload support through proxy as well?