![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
There has been a lot of discussion here lately regarding PHP. I must admit I am totally ignorant about it. Until now I've never even been curious about it. I've guessed it was something for those poor underpriviledged people that have applications outside the DBMS. The model I like is one with a really thin web-server. |
|
All I feel I need there is the absolute minimum required to securely and efficiently act as a go-between between clients (browsers) and Pick/MV processes running PickBasic code on the database/application server. All I want to store on the web-server are binary images etc. that the web-server can send to the client as required along with the data being sent out the door from the database/application server. What can PHP do that I can't more easily and efficiently do in PickBasic on the database/application server? |
|
Mike. |
#3
| |||
| |||
|
|
There has been a lot of discussion here lately regarding PHP. I must admit I am totally ignorant about it. Until now I've never even been curious about it. I've guessed it was something for those poor underpriviledged people that have applications outside the DBMS. The model I like is one with a really thin web-server. |
|
All I feel I need there is the absolute minimum required to securely and efficiently act as a go-between between clients (browsers) and Pick/MV processes running PickBasic code on the database/application server. All I want to store on the web-server are binary images etc. that the web-server can send to the client as required along with the data being sent out the door from the database/application server. What can PHP do that I can't more easily and efficiently do in PickBasic on the database/application server? |
|
Mike. |
#4
| |||
| |||
|
|
michael (AT) preece (DOT) net wrote: There has been a lot of discussion here lately regarding PHP. I must admit I am totally ignorant about it. Until now I've never even been curious about it. I've guessed it was something for those poor underpriviledged people that have applications outside the DBMS. The model I like is one with a really thin web-server. PHP is now a part of the Apache web server, that has some huge part of the web server market. So, ISPs and others often have it available. All I feel I need there is the absolute minimum required to securely and efficiently act as a go-between between clients (browsers) and Pick/MV processes running PickBasic code on the database/application server. All I want to store on the web-server are binary images etc. that the web-server can send to the client as required along with the data being sent out the door from the database/application server. What can PHP do that I can't more easily and efficiently do in PickBasic on the database/application server? Interest a 22-year old CS major? |
|
Also, I can't write something in DataBASIC for U2 that gets executed after I type in a URL (or access one). |
|
You can write PHP code that is executed with POSTs or GETs from html/javascript. I'm sure there are other good reasons, but I only know why I have wandered into it and about to write code in a language that puts dollar signs in front of variable names after avoiding Perl for all these years. |
#5
| |||
| |||
|
|
PHP is now a part of the Apache web server |
#6
| |||
| |||
|
|
Also, I can't write something in DataBASIC for U2 that gets executed after I type in a URL (or access one). You'd probably like FlashCONNECT then. |
|
You can write PHP code that is executed with POSTs or GETs from html/javascript. I'm sure there are other good reasons, but I only know why I have wandered into it and about to write code in a language that puts dollar signs in front of variable names after avoiding Perl for all these years. Well - given that the code that gets executed from a POST or GET is a PickBasic subroutine, in my case - I'd be interested to know more about those "other good reasons". |
|
Unless/until FC is available on UV it might interest you to look at Coyote - if you'd like to run things directly from DataBasic inside UV. Alternatively, can you use PHP to simply "hand-ball" things on to a waiting process on UV? I guess what I'm asking is : how much does PHP help and how much would I find it getting in the way? Cheers Mike. |
#7
| ||||
| ||||
|
|
Try parsing and building an XML document natively in FC. Also, PHP is a server module that runs in parallel with Apache. There is no need |
|
for a DB, unless you want to read/write data from one. SQL support is native. |
|
You can write PHP code that is executed with POSTs or GETs from html/javascript. I'm sure there are other good reasons, but I only know why I have wandered into it and about to write code in a language that puts dollar signs in front of variable names after avoiding Perl for all these years. Well - given that the code that gets executed from a POST or GET is a PickBasic subroutine, in my case - I'd be interested to know more about those "other good reasons". True, if you have framework in place to handle HTTP requests. |
|
Unless/until FC is available on UV it might interest you to look at Coyote - if you'd like to run things directly from DataBasic inside UV. Alternatively, can you use PHP to simply "hand-ball" things on to a waiting process on UV? I guess what I'm asking is : how much does PHP help and how much would I find it getting in the way? Cheers Mike. I guess I really need to get working on MVWWW v2.0. Using PHP with calls to MV allows you to do a lot of external stuff without having to monkey with MV. You can easily handle XML services without having to code any XML stuff in dataBASIC. Basically, it comes down to application design. If you don't like any other language except dataBASIC, then your options are quite limited but you can achieve web intergration. If you're open to using multiple technologies in combination with MV, then you have a huge playing field. |
#8
| |||
| |||
|
|
dawn wrote: PHP is now a part of the Apache web server The Apache you are referring to is the Apache Software Foundation(ASF), of which the HTTP Server is one of their many projects. PHP is not part of the Apache HTTP Server project, not one of its subprojects, nor is it even part of the ASF. |
|
On the ASF website (apache.org) you will find a link to the organization responsible for PHP (php.net), but that's about it. And on the PHP website you'll find a link to the ASF - That's about it there too. Just wanted to clear that up. |
|
-- Kevin Powick |
#9
| |||
| |||
|
|
On 9 Nov 2005 17:12:15 -0800, michael (AT) preece (DOT) net wrote: Also, I can't write something in DataBASIC for U2 that gets executed after I type in a URL (or access one). You'd probably like FlashCONNECT then. FlashCONNECT != PHP Try parsing and building an XML document natively in FC. Also, PHP is a server module that runs in parallel with Apache. There is no need for a DB, unless you want to read/write data from one. SQL support is native. |
|
You can write PHP code that is executed with POSTs or GETs from html/javascript. I'm sure there are other good reasons, but I only know why I have wandered into it and about to write code in a language that puts dollar signs in front of variable names after avoiding Perl for all these years. Well - given that the code that gets executed from a POST or GET is a PickBasic subroutine, in my case - I'd be interested to know more about those "other good reasons". True, if you have framework in place to handle HTTP requests. Unless/until FC is available on UV it might interest you to look at Coyote - if you'd like to run things directly from DataBasic inside UV. Alternatively, can you use PHP to simply "hand-ball" things on to a waiting process on UV? I guess what I'm asking is : how much does PHP help and how much would I find it getting in the way? Cheers Mike. I guess I really need to get working on MVWWW v2.0. Using PHP with calls to MV allows you to do a lot of external stuff without having to monkey with MV. You can easily handle XML services without having to code any XML stuff in dataBASIC. Basically, it comes down to application design. If you don't like any other language except dataBASIC, then your options are quite limited |
|
but you can achieve web intergration. If you're open to using multiple technologies in combination with MV, then you have a huge playing field. |
#10
| |||||
| |||||
|
|
Don't get me wrong here. I *do* like PickBasic. As I've said before - there is simply *no* better language to use in/with a Pick DBMS. Outside of Pick of course, PickBasic is nothing at all. Also, if I'm faced with having to manipulate text strings anywhere on the server side I feel most comfortable about doing that in PickBasic - regardless of whether I'm interacting with the database. I also like the fact that I can easily jump out of Pick down to the host OS to do things (like Unix !sorts) and back. As an aside - I do wish the non-Pick world was |
|
better at handling delimited text strings. Imagine if Pick-like data, with char(254)... char(253)... etc. delimiters except with nesting way beyond the subvalue level, was the accepted way to represent nested data - rather than XML. Wouldn't that be a hoot?! Talk about the ball being on the other foot! It'd be our ball park and we'd win every game! |
|
I'm OK with JavaScript for manipulating the DOM and stuff on the client side. I also like the fact that there is a huge amount of (free) tried and tested js functions out there if I need to google for it. That said |
|
- I don't love the client-side environment - there seem to be an awful lot of gotchas to look out for - but, as someone else said recently, I don't own the horse, I just gotta ride it. |
|
PHP might well be the bees knees for doing things on the middle tier - the web server. I don't doubt it. I just need to see clearly what it adds to the mix. |
![]() |
| Thread Tools | |
| Display Modes | |
| |