<x-flowed iso-8859-1>À (At) 13:00 -0500 05/02/02, Rogers Cadenhead écrivait (wrote) :
>I like Radio Userland because of all the things UserTalk and the
>object database can do, but I don't have much use for the things RU
>makes easy, such as the weblogging interface.

If you write your own upstream driver (and its not so difficult and
if you reuse UserLand code) you can have a framework where some files
are uploaded by FTP and other by xml-rpc. Now that's interesting
because you could have any type of scripting environment at the
server end. But if for example, you have a Frontier server, you can
simply in a file have a directive to tell RU to move the file by
xml-rpc in the Frontier database while other files are moved by FTP
for static rendering. I already developed such a framework for a
client and it work well. What is interesting about this is that you
still have RU macros evaluated at the upstreaming stage but not
Frontier macros (if you choose the '{}' delimiters for macros for the
Frontier server).

For example:

#typeOfUpstream "xml-rpc"

<%time from Radio: clock.now()%>
{"time from Frontier: " + clock.now ()}

---

{setString (english:"The price of the room taxes included is ",
french: "Le prix de la chambre TTC est ")} {price} {currency}.

---

What is ultra cool in this kind of framework is that you can get rid
of a lot html in code in your UserTalk code on the Frontier server.


Cheers
-Emmanuel


--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Emmanuel Décarie - Consultant
Programmation pour le Web - Programming for the Web
UserLand Frontier - Perl - JavaScript - AppleScript - HTML - XML
http://www.scriptdigital.com

---> The Frontier Newbie Toolbox:
<http://www.scriptdigital.com/fnt/frontierNewbieToolbox.html>

</x-flowed>

Enclosures

None.  

Replies

None.