Perl LWP like scripting from Rev?
soapdog at mac.com
Wed Mar 31 20:42:37 CST 2004
On Mar 31, 2004, at 6:49 PM, Jim Witte wrote:
> Is there any way I can automate website interaction in Rev, similar
> to the Perl LWP module (or perhaps calling LWP directly from Rev?)
don't know what you want, but allow me to talk a little about a project
of mine and about another solution, both will deliber WebApp
functionality, I grok that for website interaction you mean dynamic
pages built in Rev, may they be CGI or not.
First, let me sell my fish. (actually give, for it's free fish)
I've got this project that was called revHTTPd, you can see more info
on it by going to my homepage http://www.soapdog.org and looking into
the projects. I'll brief here what revHTTPd is at the first glance.
First it was a full HTTP server built in Rev that was able to serve
static and dynamic pages. Dynamic pages were just substacks of the
server and this server could be embedded in any stack of yours. You can
look at my home server by pointing your browser to
http://home.soapdog.org:8081/ there you can see the server running and
interact with it, also learn about it's internals.
Now let me talk deeper on revHTTPd or more, on ServerWorkz, which is a
bundle that integrates many things.
revHTTPd now is not only a server, it's a WebSever+DB+Development
Framework and it's bundle is called ServerWorkz.
ServerWorkz as a WebServer:
This is revHTTPd core, it's a collection of front and back scripts that
gives plug and play webserver functionality to any Stack. Out of the
box, it's able to serve static and dynamic files, it's also able to do
a lot of stunts with templates and automatic data transportation (from
html form data to Rev Stacks), you might know about this from About
link in my home server running at http://home.soapdog.org:8081/
ServerWorkz as a DB Conduit:
Since we have automatic and transparent data transportation from and to
web forms. To take a step further and glue a database to it was easy.
We can store Session data in Databases (stackbased, XML or MySQL). This
way you just create your database, make a stack to interact with it and
ServerWorkz will take care of making that stack a webapp.
ServerWorkz as a Development Framework:
The API that drive ServerWorkz is simple, my motto is: LESS IS MORE. I
made simple functions one should call when making their own custom
stacks. It's all plain easy very high level API, it's straight forward,
you call http_flush and send data, you call http_redirect and redirect
the browser, you query an array and receive web data, it's all direct
with the most minimum handlers. This way you can keep thinking on your
app login instead of struggling with my API. Since I use this system on
my own to deliver solutions for my clients, I trust me to empower this
API to suit my needs, so in the end everyone benefits from it. This is
not a product I am selling, this is what I actually use to make money,
and I am sharing it for I think we can all make more money togheter.
So as you saw quick, you can deliver custom HTTP Server with tons of
features. But if you've got your nice apache running and don't want to
launch another server you can always trust LibCGI to do the job for
you. It's a very nice and high level lib that will take care of many
things, from redirections to cookies and beyond. I learned much from
this lib and it was a invaluable tool on the development of the next
generation of ServerWorkz.
Also, you can always talk to us on your projects so that you do not
have to reinvent the wheel!
> use-revolution mailing list
> use-revolution at lists.runrev.com
Andre Alves Garzia ð 2004 ð BRAZIL
More information about the use-livecode