Re: Which Is The Better Approach To Working With Javascript?
- From: "Barry" <no.one@xxxxxxxxxxx>
- Date: Wed, 9 Jul 2008 13:46:59 -0500
"Jerry Stuckle" <jstucklex@xxxxxxxxxxxxx> wrote in message
news:g52uh3$66v$2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
The Natural Philosopher wrote:
Jerry Stuckle wrote:
Ivan Marsh wrote:My last one cost me nothing more than a hard disk actually. The PC was
On Wed, 09 Jul 2008 07:59:50 -0400, Jerry Stuckle wrote:
bill wrote:
Jerry Stuckle wrote:And how about the second part of the question - what hosts have such
Ivan Marsh wrote:http://en.wikipedia.org/wiki/Server-side_JavaScript
On Tue, 08 Jul 2008 17:27:08 -0400, Jerry Stuckle wrote:What interpreters are available for javascript on the server, and
Patient Guy wrote:Except that you can run server-side javascript... though I don't
Jerry Stuckle <jstucklex@xxxxxxxxxxxxx> wrote in comp.lang.php:That is correct. Javascript runs on the client. Communications
Patient Guy wrote:So, based on your response, you are telling me that a PHP
Which is the better approach in working with Javascript?3. Try a javascript newsgroup. This one is for PHP.
1. Server side processing: Web server gets form input, runs it
into
the Javascript module, and PHP collects the output for document
prep.
2. Client side processing: Web server gets form input and
passes it
to PHP which includes the Javascript written in a way to make
the
form input processed on the client side and rendered (probably
using
DOM function calls) on that side as well.
I posted this <news:Xns9AD554BCD7E9FUVAA@xxxxxxxxxxxx> in an
apparently less trafficked newsgroup and the post was the TLDR
kind,
but it has the background and details of why the code must be
in
Javascript and why PHP must work with it somehow. It also
gives the
details of the server and how it forks and communicates with
processes to parse/generate output.
processing
implementation has no interprocess communication capability, or
ability
to interface with a (Java)script interpreter.
Hint: javascript does NOT run on the server.A server, or a server-associated process, can start a script
host,
passing some form of input to it, and the script host does the
script
interpretation, while the calling process waits for output.
However this is achieved, PHP (by design?) has no script
interface,
based on your response.
between
PHP and javascript is limited. PHP can generate javascript code,
and
javascript can submit data to the server for PHP to process.
But there is no javascript interpreter on the server. That is the
browser's job.
know why
you would want to.
what hosts have it installed?
It is not part of the package of any web server.
packages installed?
I'd expect you'd have to be running your own server to use any of it.
Why is that? Servers are expensive for a relatively small site.
free..too old to run bleeding edge Vista I expect.
I already had a static IP address..just arrange some pass through and I
have my own linux/apache/Mysql/php setup that is under my control.
OK its not got big ISP backup, and only 448kbps upload, but its more than
enough for 'small sites'
And what do you do when you have a power outage? Or your phone line goes
down? Or the server crashes the day after you leave on a two week
vacation?
Of even when your host blocks port 80 because it violates their TOS?
Home hosting can be OK for hobby sites, but even a small business site
needs to be reliable.
what a hair-splitter, jerry! every major host has different level service
plans including small business plans...which are NOT expensive. further,
none of the hosts i've used blocks 80 AND even non-static ip addressed
accounts are 'non-static'. i've had dhcp from charter for 8 years running a
small business. the ONLY time my IP has changed (twice, as a matter of fact)
is because I called them to complain about faulty equipment. changing the
IP, for them, is a manual process that happens upon the initialization of a
modem. that's it. there is NOTHING in the TOS about running your own
website...they just say they won't guarantee your uptime/accessibility. on
the business plan, you simply get faster service response and some roll-over
backup mechanisms when an outage occurs...and a guarantee that your IP won't
change upon device initialization (et. al).
again though, you're simply skirting the fact that you said javascript is
client-side only. you're diverting attention from that fact by bring up over
and over again that few servers support server-side javascript (which you
say doesn't exist in the first place). just own up to the mistake and leave
it at that. sabelotodo!
.
- References:
- Which Is The Better Approach To Working With Javascript?
- From: Patient Guy
- Re: Which Is The Better Approach To Working With Javascript?
- From: Jerry Stuckle
- Re: Which Is The Better Approach To Working With Javascript?
- From: Patient Guy
- Re: Which Is The Better Approach To Working With Javascript?
- From: Jerry Stuckle
- Re: Which Is The Better Approach To Working With Javascript?
- From: Ivan Marsh
- Re: Which Is The Better Approach To Working With Javascript?
- From: Jerry Stuckle
- Re: Which Is The Better Approach To Working With Javascript?
- From: bill
- Re: Which Is The Better Approach To Working With Javascript?
- From: Jerry Stuckle
- Re: Which Is The Better Approach To Working With Javascript?
- From: Ivan Marsh
- Re: Which Is The Better Approach To Working With Javascript?
- From: Jerry Stuckle
- Re: Which Is The Better Approach To Working With Javascript?
- From: The Natural Philosopher
- Re: Which Is The Better Approach To Working With Javascript?
- From: Jerry Stuckle
- Which Is The Better Approach To Working With Javascript?
- Prev by Date: Re: Which Is The Better Approach To Working With Javascript?
- Next by Date: Re: Which Is The Better Approach To Working With Javascript?
- Previous by thread: Re: Which Is The Better Approach To Working With Javascript?
- Next by thread: Re: Which Is The Better Approach To Working With Javascript?
- Index(es):
Relevant Pages
|