[Laszlo-dev] Serverless deployment
wweems at gmail.com
Tue Oct 26 13:48:19 PDT 2004
what exactly is the ultimate goal? the samples of that xml-rpc
implementation look to me very much like the remote scripting
implementations I've used. THe one I primarily use is usable in many
On Tue, 26 Oct 2004 13:29:48 -0700, Andrew Wooldridge
<triptych at gmail.com> wrote:
> updated it's been:
> On Wed, 20 Oct 2004 16:57:30 -0400, Oliver Steele
> <steele at laszlosystems.com> wrote:
> > [Hey everyone, what follows is the *exact same message* that I just
> > sent under the title "Re: [Laszlo-dev] .net port". I'm resending it
> > with a new title so that it will be easier to track the two
> > discussions. Please reply to this message, not the other one, if you
> > want to talk about serverless deployment. Sorry about that, but I
> > think it will make life easier in the long run...]
> > On Oct 18, 2004, at 6:24 PM, Weston Weems wrote:
> > > As far as contributing to offline compiler project, anyone got any
> > > sort of status or anything of that nature?
> > >
> > > Or stuff that needs work?
> > Thanks for asking. This would be a great area for contributions.
> > We actually have an offline compiler now (it's the 'lzc' script, which
> > invokes com.laszlosystems.compiler.Main); what we don't have is a way
> > for the compiled application to make data, media, or RPC requests.
> > This latter set of features is what we're calling "serverless
> > deployment." (I'm sure Weston understands the distinction, I just
> > wanted to normalize our terminology in case this thread gets mixed into
> > other discussions.) So we're really looking at four things:
> > 1. Compiling a Laszlo application into a swf, and serving this swf from
> > outside LPS. Call this a "statically served swf."
> > 2. Allowing a statically served swf to make data requests (<dataset
> > src="http:...">)
> > 3. Allowing a statically served swf to make media requests (<view
> > resource="http:...">)
> > 4. Allowing a statically served swf to make RPC (SOAP, XML-RPC, and
> > JavaRPC) calls.
> > (1) is possible now, but it's difficult to use the prebuilt binary for
> > this. (That binary doesn't include lzc, and it doesn't include the
> > Java class --- com.laszlosystems.compiler.Main --- that lzc invokes.)
> > You have to request the application from a browser, and then look in
> > the application cache of the server --- or perhaps more usably, look in
> > the browser cache or use wget or curl to retrieve the swf file, and
> > copy it to your Apache or other static server.
> > This gives you an application that can't make requests to the server.
> > Even with this limitation, this would be useful for some applications.
> > A useful contribution would be to write up step by step instructions on
> > how to use the LPS as a development environment, for creating a static
> > swf that can be deployed with Apache.
> > (2) Data requests: Henry has got this partly working in the current
> > development branch. Sorry, you don't have the sources for this yet ---
> > we're rushing to put together an updated source release that includes
> > this work and release this to OpenLaszlo, and when this happens we can
> > point you at the code for this.
> > (3) Media requests: This is isn't ready for outside work yet --- it
> > requires a version of the LPS that can create swf6 files, and that's
> > the same development branch that we haven't published yet.
> > (4) RPC: The current SOAP and XML-RPC implementations rely on adaptor
> > code on the server. For serverless deployment, we would need a
> > already exist, that could be integrated into the product? (Even if it
> > didn't have a compatible license, if there were some glue code that let
> > it work with the Laszlo runtime we could point people at that, for a
> > serverless solution.)
> > This has the advantage that you can work on it using today's source
> > distribution (for LPS 2.2). The RPC code hasn't been changed between
> > that distribution and the internal development branch.
> > By the way, before we can actually accept any work, we need to get you
> > a contributors license. You should be able to get started on (1) and
> > (4) independently of that, though, and also (2-3) once you have the
> > latest sources, if any of these projects seems interesting to you.
> > Best,
> > Oliver
> > --
> > Oliver Steele
> > Chief Software Architect
> > Laszlo Systems, Inc.
> > _______________________________________________
> > Laszlo-dev mailing list
> > Laszlo-dev at openlaszlo.org
> > http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
> Laszlo-dev mailing list
> Laszlo-dev at openlaszlo.org
More information about the Laszlo-dev