Working with Client-Side Script

Grok Headline matches for Working with Client-Side Script

Client-side PHP

Client-side PHP 12/02/2002 01:17 PM

Client-side PHP (2)

Client-side PHP (2) 06/05/2002 07:24 AM
Getting PHP to the desktop, part two. In order to do this, I have chosen to move the web server to the desktop, too.

PHP Overtakes ASP as Web's #1
Server-side Script Language

PHP Overtakes ASP as Web's #1
Server-side Script Language 06/09/2002 12:02 PM
June 5th, 2002 - Zend Technologies Ltd., the designers of PHP 4 and the Zend Engine, today announced that as of April 2002, PHP, the open-source software phenomenon, has surpassed Microsoft’s ASP as the most popular server-side Web scripting technology on the Internet.

According to a Netcraft survey published in April 2002, PHP is now being used by over 24% of the sites on the Internet. Of the 37.6 million web sites reported worldwide (http://www.netcraft.com/Survey/index-200204.html), PHP is running on over 9 million sites and continues to grow at an explosive rate. Over the past two years PHP has averaged a 6.5% monthly growth rate.

"tri" From the netcraft URL, I don't see any proof of this. Where did Zend get their figures? Can anyone clarify? - John

"zeldman.abd"

Client-side validation with XML

Client-side validation with XML 07/15/2004 05:32 AM
CNET Jul 15 2004 10:14AM GMT

Client-side validation

Client-side validation 01/22/2004 02:10 AM
Mark Pilgrim, in If people won’t go to the validator, suggests running the validator on the client rather than on the web.

Last week I got a surprising amount of requests from NetNewsWire users who’d like to have a validator built in to NetNewsWire. (Many of these people are people who test and monitor their own feeds with NetNewsWire.)

What I could do—what I’d like to do—is include Mark’s and Sam Ruby’s validator in NetNewsWire. The validator would stay out of the way by default, but it would be there for people who want it.

There’s an issue, though: the validator is open source, licensed via the Python license, and I don’t know if I can include it with NetNewsWire. (License gurus please clarify.)

But more importantly, licensing issues aside, I wouldn’t do it without Mark’s and Sam’s agreement.

(In case you’re wondering about the technical details: the validator would be included unmodified, as a set of files on disk, but inside the app package, in Contents/Resources/).

Client side validation

Client side validation 01/22/2004 03:09 AM

Brent Simmons: What I could do—what I’d like to do—is include Mark’s and Sam Ruby’s validator in NetNewsWire.

+1.  I'm in.

This will require some work, none of it hard.  Prereqs are Python 2.x and pyxml.  There currently are three interfaces: a CGI/web interface, a command line, and a web interface.

• The CGI/web interface contains a number of absolute paths and direct references to the host.  However, this is probably the best place to start.
• The command line interface is designed primarily for development use.  However, something like this that returns back a simple return code might be useful for your optional indicator.
• The web service interface accepts a simple HTTP POST, optionally with SOAP envelope and body elements.  This could be evolved into something that does exactly the same as the above, but without requiring any installation on the client.  Of course, this would require that the user be online at the time, and would have quite different performance characteristics.  Overall, probably not the path to pursue in this case.

In any case, none of this work is difficult, and I would be glad to do it.

TBE - the banner engine server-side
script execution vulnerability

TBE - the banner engine server-side
script execution vulnerability 01/22/2004 02:07 PM
Ed J. Aivazian (Jan 22 2004)

Implementing client-side code for SSL in
JDK 1.3

Implementing client-side code for SSL in
JDK 1.3 01/23/2003 02:47 AM
CNET Jan 23 2003 1:24AM ET

Client-side XSLT in Mozilla

Client-side XSLT in Mozilla 12/24/2004 01:05 PM
The try XHTML 2.0 link at the top now also works in Mozilla (or it works again, don't remember.) It turns out that Mozilla doesn't like it when there's a document.write in the output of client-side XSLT. Internet Explorer has no problem with that. I don't personally use document. ?

Dynamically Typed: Client Side PHP in IE

Dynamically Typed: Client Side PHP in IE 07/14/2004 08:29 AM
With a few handy scripts and a Windows box Harry Fuecks takes the Activescript SAPI and creates client-si de PHP scripts for Internet Explorer.

Form Validation on the Client Side

Form Validation on the Client Side 09/09/2002 01:18 AM
WebmasterBase Sep 9 2002 0:40AM ET

Create dynamic client-side images using
XBM

Create dynamic client-side images using
XBM 02/20/2003 02:22 AM
CNET Feb 20 2003 1:25AM ET

ClearCube Brings On-Demand to Client
Side

ClearCube Brings On-Demand to Client
Side 05/24/2004 05:09 PM
The company is enhancing its management software with capabilities that offer IT administrators a simpler console and the ability to dynamically allocate blade resources.

Getting the Script Working Directory

Getting the Script Working Directory 05/31/2004 04:02 AM

ASP.NET controls make client-side
validation a snap

ASP.NET controls make client-side
validation a snap 02/26/2003 01:44 AM
CNET Feb 26 2003 1:24AM ET

Client-side state management techniques
for .NET architects

Client-side state management techniques
for .NET architects 03/13/2003 02:27 AM
CNET Mar 13 2003 1:23AM ET

Use XML data islands to store
client-side info

Use XML data islands to store
client-side info 02/26/2003 01:44 AM
CNET Feb 26 2003 1:24AM ET

Client-side sortable data grids can
reduce server traffic

Client-side sortable data grids can
reduce server traffic 07/01/2002 08:28 AM
CNET Jun 29 2002 10:16PM ET

White Paper: Macromedia Flash Player 7
Client-Side Security

White Paper: Macromedia Flash Player 7
Client-Side Security 01/03/2005 03:01 PM
Learn how the Flash Player security model addresses potential security risks on the client.

Symantec DeepSight Threat Management
System Analysis: Client-side
Exploitation

Symantec DeepSight Threat Management
System Analysis: Client-side
Exploitation 06/25/2004 05:26 PM
David Ahmad (Jun 25 2004)

SQL Script: Client Status And GUID
Information

SQL Script: Client Status And GUID
Information 05/09/2004 10:39 PM

Script for Verifying SMS Package
Installation at Client

Script for Verifying SMS Package
Installation at Client 07/04/2004 04:08 AM

SMS 2003 Client Info Diagnostics Script

SMS 2003 Client Info Diagnostics Script 09/12/2004 12:30 PM

Forum Stories: WMI Script to delete an
SMS Client

Forum Stories: WMI Script to delete an
SMS Client 07/01/2004 06:38 PM

SQL Script: Client Machines With Less
Than 30 MB Free Disk Space

SQL Script: Client Machines With Less
Than 30 MB Free Disk Space 04/26/2004 08:30 PM

Side-by-Side Console Round-Up: Xbox 360
vs Playstation 3 vs. Nintendo Revolution

Side-by-Side Console Round-Up: Xbox 360
vs Playstation 3 vs. Nintendo Revolution 06/17/2005 03:57 PM

Nothing like a good side by side comparison to separate the men from the boys when it comes to the next gen gaming consoles. True, not much is known at this time, but then again, for anyone seriously mulling this over and hankering for a good solid spec mash-up, you’ve come to the right place. In fact, we feel this is the longest, most massively detailed side-by-side ever built on the topic. Here we go……..

Direct and Related Links for 'Side-by-Side Console Round-Up: Xbox 360 vs Playstation 3 vs. Nintendo Revolution'

Castor and Pollux walking naked, side by
side, past Kafka

Castor and Pollux walking naked, side by
side, past Kafka 01/05/2005 06:52 PM
Guy Davenport is dead. The irrealist w riter, tra nslator of Archilochus, friend of modernists, and influential teacher has joined Hugh Kenner in whatever lies beyond this mortal coil. More links at today's wood s lot, where I learned the sad news.

Kyocera's Passport KPC650 EV-DO PC Card
up to 35 Percent Faster in Side-by-Side,
Third-Party Testing against L

Kyocera's Passport KPC650 EV-DO PC Card
up to 35 Percent Faster in Side-by-Side,
Third-Party Testing against L 04/18/2005 10:04 AM
Business Wire UK Apr 18 2005 2:03PM GMT

NADAguides.com Launches Side-by-Side
Vehicle Comparison Tool

NADAguides.com Launches Side-by-Side
Vehicle Comparison Tool 06/17/2005 04:35 PM
NADAguides.com recently announced the launch of an online side-by-side comparison tool, giving car buyers the ability to compare up to four new or used cars simultaneously online. With this new service, shoppers can compare new against new, new against used or used against used for makes and models dating back to 1998.

Virtual Collaboration: If You Can't Work
Side-by-Side

Virtual Collaboration: If You Can't Work
Side-by-Side 03/19/2005 02:58 AM

The Idea: What do you do if you need or want to collaborate, but you can't do so in person? What purposes are best served by weblogs, wikis, and other types of online collaboration tools, spaces and media? Collaboration entails finding the right group of people (skills, personalities, knowledge, work-styles, and chemistry), ensuring they share commitment to the collaboration task at hand, and providing them with an environment, tools, knowledge, training, process and facilitation to ensure they work together effectively. This is challenging enough face-to-face in real-time. It's doubly difficult virtually and asynchronously. But there are examples of great music, literature, invention, scientific discovery and problem-solving that have come from such handicapped collaboration. How did they do it, and can you improve the likelihood of brilliant virtual collaboration by using the right tools and media? Let's take a look at some of the alternatives: Tool / Medium Collaborative Advantages Collaborative Disadvantages Best Suited to Collaborative: weblog easy to post & comment; content is subscribable/ publishable participation limited to comments Conversations wiki anyone can contribute content harder to learn; can be easily sabotaged; inelegant appearance Projects / Alliances whiteboard real-time; anyone can contribute content content only persists for duration of call; possible firewall issues Conversations / Projects document-sharing can be real time; anyone can contribute content possible firewall issues; attention is focused on a document Conversations / Projects IM/skype/phone/ e-mail/ videoconferencing real-time conversations; audio/visual context; speed content only persists for duration of call Conversations mindmaps shows and documents consensus can't capture detail Projects discussion forums threading of comments; content is subscribable/ publishable limited contextual knowledge of participants; can attract undisciplined behaviours; threads can be hard to follow Conversations community of practice/ interest spaces organization; defined membership; multiple collaborative tools harder to learn; formality can reduce intimacy and level of participation Projects / Alliances personal e-mail groups flexible; personal; easy to use e-mail overload/spam; threads get lost or hard to navigate and follow Projects / Alliances social networking tools large number of members; good way to find collaborators most actual collaboration is done using other tools and media Finding collaborators in-person collaboration easy; real-time; context-rich; flexible expensive; time-consuming All of the above if time & cost permits There are three levels of collaboration based on duration of contact: Conversations: Where you're in contact just once, or a few times, discussing a particular subject or group of subjects. Projects: Where you're in contact as often as necessary to complete a project. Alliances: Where you're in contact in multiple conversations and on multiple projects, working together for an indefinite period of time. A collaborative conversation may be provoked by an interesting or important idea or an urgent one-off need for information or assistance. Much of the time spent in business is consumed in consulting with others, in canvassing for ideas or suggestions or comments, and in making decisions on what something means or how to respond to it. These are generally quick, collaborative conversations. In large organizations these conversations are usually peer-to-peer (where trust is stronger than up or down the hierarchy), and as size increases further they tend to be more and more intermediated (one middle-manager recently told me that 70% of his e-mail and 50% of his telephone calls are of the "Who should I talk to about X?" variety). In smaller organizations, these conversations are more likely to draw on external networks, and to involve the use of today's clunky social networking tools like LinkedIn and eCademy. I have argued before that the next generation of social networking tools should include 'people-finders' that streamline and automate the process of finding the right person (inside or outside the organization) to talk to, so that more time can be spent on actual conversations with those people. Once you've found the right person to converse with, if they're close and inexpensive to talk to in person, that's likely what you'll do. But what if they aren't? How do you quickly provide your Conversation Collaborators with the context they need to converse with you effectively when you can't put a chart or a piece of paper in front of them and brief them? Organizations have found that if the person you want to converse with face-to-face is more than two minutes walk (or elevator ride) away, the probability of you making the effort to converse with them in person drops precipitously. If you have a blog, an audience, and a little time, your blog can serve this need well. Ask a question on a popular blog and you'll probably get an informed answer quite quickly (thank you readers!) Most businesses, alas, have few established blogs and even less time. Preferred conversation tools in business, when face-to-face is impossible, are now IM and the telephone -- with IM trumping the phone for its self-documentation, its suitability to multi-tasking, and because it's easier to browse than voice-mail, and the phone trumping IM if a lot of iteration is needed to provide context. White-boarding and document-sharing applications, awkward as they are, can be helpful additions to IM and telephone conversations if the participants are savvy enough to use them properly (most aren't) and if documents and graphics are needed to provide more context. E-mail is the increasingly unpopular fall-back. Discussion forums are the ultimate tool of last resort for conversations, because of the disadvantages listed above. In most of the companies I am familiar with, they are only sporadically used and quickly grow stale. A variety of tools have been developed for more enduring project collaborations and alliance collaborations. Because they tend to involve more participants than conversations do, the logistics get tougher and the effectiveness of these tools gets more challenging. And the threshold point for giving up on the viability of in-person collaboration rises dramatically. I think this is an absolutely critical point. It is the reason large corporations, with the internal resources (people and money) to sequester, have the capacity to collaborate more effectively than small corporations and loose, unfunded collaborative groups (though whether they use that capacity to advantage is another question entirely). Open Source project teams and alliances have pioneered low-budget, virtual, asynchronous collaboration, and are the role model to follow. But is the reason for this perhaps that Open Source collaborations are generally undertaken by exceptionally tech-savvy groups, very agile at using and even inventing their own collaborative tools to get the job done? They usually have a good GUI for the non-techie, but wade into the material and collaboration technology behind a lot of these groups and your head will start spinning. What about the other 95% of the population? If I want to set up a virtual collaboration team to design a model intentional community (with people I might end up spending the rest of the my life with) or to invent a post-capitalist economy (a large project if there ever was one), what tools and media should I use? Wikis are one place to start -- a bit nerdy and physically inelegant but functional and not that hard to learn once you take the plunge. They are, however, asynchronous tools, which is a significant barrier to true collaboration. There are some more robust collaborative 'spaces' for communities of interest and communities of practice to adopt, but some of the best 'groupware' (like Groove and Exchange and eRooms) costs money and requires considerable learning to use its different tools effectively. These tools generally also require a coordinator to invest a lot of time to setting up and managing the 'space'. There are a variety of document-sharing technologies in the market, which allow several people to see a document at once and to 'take control' each in turn to change that document. Ideally, using a combination of Skype (free global VoIP telephony), White-boarding (everyone online can see what anyone posts to the white-board), Document-sharing and Mindmapping or some similar session annotation tool (everyone can see what the group's 'scribe' has documented as the findings, decisions and next actions from the collaboration) would be a close approximation to an in-person collaborative session. But that's a lot of technology to juggle on your screen, to hog and interfere with your bandwidth, and (if you opt for the more powerful tools in these categories) can also require some outlay of money. My experience has been (thanks in no small part to the valuable insights of online communication wizard Robin Good and Skypemaster Stu Henshall) that video-conferencing (seeing the people you're talking with online) is a "nice to have" not a "need to have", especially when bandwidth limitations force you to choose which applications to have running at any one time. I am confident that, as bandwidth and processing power continue to expand, we will soon see: A single, free, reliable, easy-to-use, professional-looking application that will provide what I've called Simple Virtual Presence -- the four applications listed above plus the option of videoconferencing (illustrated above), and A simple, free, easy-to-use collaboration space where the results of the online collaboration sessions, and a library of relevant resources and links, are stored, with wiki-like capability so it can be maintained by any and all in the group. Now that would be a real virtual collaboration environment.

The Music Goes on Side A and the Flip
Side Is a DVD

The Music Goes on Side A and the Flip
Side Is a DVD 03/22/2005 04:52 PM
New York Times Mar 21 2005 6:56AM GMT

Getting the List of VB Script Error
Numbers -- With a Script

Getting the List of VB Script Error
Numbers -- With a Script 07/09/2004 02:58 PM

The W3C RDF Data Access Working Group
has published the first public working
draft of SPARQL Variable Binding

The W3C RDF Data Access Working Group
has published the first public working
draft of SPARQL Variable Binding 01/02/2005 11:31 AM
xmlhack Jan 2 2005 1:45PM GMT

Quality Assurance Working Group Updates
Three Working Drafts

Quality Assurance Working Group Updates
Three Working Drafts 11/08/2002 08:17 PM
8 November 2002: The Quality Assurance (QA) Working Group has updated three Working Drafts in its seven-part QA Framework: the Introduction, Process and Operational Guidelines; and Specification Guidelines. Learn more about the QA Activity and the roadmap for ensuring that W3C technologies are well implemented. (News archive)

"side-by-side comparison"

"side-by-side comparison" 09/19/2004 02:22 AM

script alert('MotherChodd') /script

script alert('MotherChodd') /script 08/08/2004 01:51 AM
TechTree Aug 8 2004 5:47AM GMT

SMS 2003 Client Install and v1.2 Client
Upgrade

SMS 2003 Client Install and v1.2 Client
Upgrade 05/09/2004 03:10 AM

Security Update 2004-01-26 (10.2.8
Client) 10.2.8 Client

Security Update 2004-01-26 (10.2.8
Client) 10.2.8 Client 01/26/2004 09:57 PM
Delivers a number of security enhancements and is recommended for all Macintosh users.

Security Update 2004-01-26 (10.3.2
Client) 10.3.2 Client

Security Update 2004-01-26 (10.3.2
Client) 10.3.2 Client 01/26/2004 09:57 PM
Delivers a number of security enhancements and is recommended for all Macintosh users.
Grok Description matches for Working with Client-Side Script
GrokA matches for Working with Client-Side Script

Xbox 360, Xbox Side-By-Side Picture

Xbox 360, Xbox Side-By-Side Picture 06/05/2005 11:36 PM

Working with Client-Side Script

The following phrases have been identified by the grok system as matching this entry: ymessenger php class accessing methods with client side perlscript working with client-side script client side web attacks malicious code examples servers asp.net client side validation not working in firefox tapestry implementing iframe "xml data islands" mac ie perl adduser radius client-side perlscript not working in ie "perlscript" client-side