Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Re: better post, get, cookie support?

From: joel:neely:fedex at: 27-Aug-2002 6:44

Hi, Andrew and Petr, Andrew Martin wrote:
> pekr wrote: > > ...could something be done about better POST, GET, cookie > > support in Rebol? >
I'd like to second (third?) that sentiment. REBOL made such great strides in unifying 'Net protocols by allowing READ to operate transparently across the local file system, HTTP, FTP, etc. on the client side, but then fell apart on the server side with all of the unnecessary complexity in handling GET vs. POST, the query string, etc. I really thing someone should have looked at the implementation of the CGI module in Perl, which can be invoked to hand back an object that simply provides all of the parameters and headers in a simple interface without having to worry about whether the request was a GET or a POST, without any complexity over getting all of the POST content, etc...
> As well, I want to make a round trip through the browser, > ... That would involve form creation, > then at least one CGI GET or POST as appropriate. >
The other thing that is severly missing is any ability to get to the environment (and I really hope somebody can show me that I've missed something here!) For example, there is a widely-used security product that handles userlogin/authentication as a plug-in to the web server. It offers very sophisticated, fine-grained management of resources, including distributed management of user identity and priveleges, workflow management for authentication/authorization, and single- sign-on capability that can span multiple servers and apps. Once a user has logged in to a protected app, this product can allow entry to any other protected app (to which that user has access, of course) without the need for another login cycle. It can be configured to pass any directory-based information about the user to the application that the user is accessing (e.g. for customization to the individual user). It passes this user information by setting environment variables (configurable by the developer) to contain whatever user-specific data is desired/needed. However, this assumes that the app (CGI) can read the environment!!! Passing configuration and data via the environment is such a frequently-used technique that I'm amazed that REBOL can't deal with it, yet I've been unable to find any way to do so. Can anybody help my ignorance, or is this a real omission? -jn- -- ; Joel Neely joeldotneelyatfedexdotcom REBOL [] do [ do func [s] [ foreach [a b] s [prin b] ] sort/skip do function [s] [t] [ t: "" foreach [a b] s [repend t [b a]] t ] { | e s m!zauafBpcvekexEohthjJakwLrngohOqrlryRnsctdtiub} 2 ]