In einer eMail vom 03.03.00 08:11:02 (MEZ) Mitteleurop�ische Zeit schreibt [EMAIL PROTECTED]: > On Thu, Mar 2, 2000, <[EMAIL PROTECTED]> wrote: > > >Having done something similar with ASP and MS-SQL Server 7, using ASP to snip . > >I can say it works. It's ugly, but it gets the job done. On the other > >hand - what [EMAIL PROTECTED] is trying to accomplish is just better > >done in PHP alone. > > >Why bother to add another layer on top of it? Just to > >use Rebol? That kind of solution flies in the face of the Rebol > >phillosophy. > > > >K I S S > > > >Keep it Simple, Stupid. > > That's what I'm trying to do. I don't think reading a PHP page to get > the time with millisecond resolution is a particularly complex task. > Reading PHP pages to access a database might very well be too hairy to > try. I haven't attempted it yet, so I don't know. > But for the real meat of what I want to do, Rebol's flexible syntax > really seems like a boon, i.e. what I want will probably take a lot more > PHP code to implement than Rebol code. > > >The simple solution is usually the best, and most correct one. When > >Rebol/Command comes out, and you can access deeper functionality using > A library for rebol could be written in perl, with a bit thinking about protokoll (a quick look at http://www.zend.com/ says PHP is similar to perl, so it may usable too:) look at rebols "predecessor" perl. When it needs a tricky function, it simply mix C in. or whatever. pretty factored in a library, and after that, it is perl. No one needs to know C to use it. perl has a similar level as rebol in handling strings and eval (do) sourcecode. So a library for rebol could be written in perl, with a bit thinking about protokoll. which can do nearly all and if not, it can C. if REBOL can communicate with things email, http and other servers, why not with a specialised proxy-server for databases or whatever? First would be a REBOL-Block <--> perl-struct converter, after that one can do pretty messaging between them. if perl starts rebol, communication with stdin/stdout between them is *very* private, i think. Then REBOL (&carl) has much (em, more) time to find ways of doing this things easy, elegant and everywhere. The old communication-protokoll should be re-implementable with /command or whatever intern, rest of code continues with "ask-db[select x y from table..]" as before.. snip > .:Eric > Volker
