NYCPHP Meetup

[Brian Pang]

I'd use checkboxes, one for each category, and an "other" checkbox with
an accompanying text field...
if "other" is checked and a value entered in the text field, during form
processing, I would add that value to my categories table.

> 
> > Hi Hans,
> > 
> > Thanks for the response.
> > 
> > What I am looking for is page widgets - HTML/JS doohickeys (technical
> term!)
> > that enhance the user experience.
> > 
> > Say you have a product that can be assigned to multiple categories -
> how are
> > you representing this on the screen, so that users can quickly
> > add/edit/delete multiple categories to that product?  Also, how to you
> let
> > them add a new category?  The emphasis is on minimizing page
> refreshes, and
> > trying to make it more like an application.  Just trying to see what
> people
> > have come up with.



>From hans not junk at nyphp.com  Wed Jul 14 13:23:08 2004
Return-Path: <hans not junk at nyphp.com>
Received: from smtp11.intermedia.net (smtp11.intermedia.net [64.78.21.10])
	by virtu.nyphp.org (Postfix) with ESMTP id F127EA86BF
	for <talk at lists.nyphp.org>; Wed, 14 Jul 2004 13:23:07 -0400 (EDT)
Received: from ehost011-1.exch011.intermedia.net ([64.78.21.3]) by
	smtp11.intermedia.net with Microsoft SMTPSVC(6.0.3790.0); 
	Wed, 14 Jul 2004 10:23:07 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [nycphp-talk] PHP Scales, Our Chris Shiflett gets /.'d
Date: Wed, 14 Jul 2004 10:23:05 -0700
Message-ID: <41EE526EC2D3C74286415780D3BA9F870311B823 at ehost011-1.exch011.intermedia.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [nycphp-talk] PHP Scales, Our Chris Shiflett gets /.'d
Thread-Index: AcRpqVwTrR5UGYC4RR2IAZdsadq0DgAHHEzw
From: "Hans Zaunere" <hans not junk at nyphp.com>
To: "NYPHP Talk" <talk at lists.nyphp.org>
X-OriginalArrivalTime: 14 Jul 2004 17:23:07.0450 (UTC)
	FILETIME=[3A8639A0:01C469C7]
X-BeenThere: talk at lists.nyphp.org
X-Mailman-Version: 2.1.4
Precedence: list
Reply-To: NYPHP Talk <talk at lists.nyphp.org>
List-Id: NYPHP Talk <talk.lists.nyphp.org>
List-Unsubscribe: <http://lists.nyphp.org/mailman/listinfo/talk>,
	<mailto:talk-request at lists.nyphp.org?subject=unsubscribe>
List-Archive: <http://lists.nyphp.org/pipermail/talk>
List-Post: <mailto:talk at lists.nyphp.org>
List-Help: <mailto:talk-request at lists.nyphp.org?subject=help>
List-Subscribe: <http://lists.nyphp.org/mailman/listinfo/talk>,
	<mailto:talk-request at lists.nyphp.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2004 17:23:08 -0000


> As an aside, the stock definition of scalability that Hans threw out
> (which is an excellent one, imho) ignores the resource cost of
scaling.
>   In general, you would prefer a solution whose cost scales linearly
(or
> better yet sub-linearly, good luck there) with cost.  What this means
> is that if you are at capacity and you double your traffic, your costs
> should double as well.  There are many applications which scale, but
> not linearly (due for example to interdependencies between services).
> These apps 'scale' but become cost prohibitive.

That's an excellent point.

It's also interesting, however, how this point is so often left out.
For instance, much of the stock definitions of scalability come from
hardware manufactures... don't forget, Java is Sun.  It seems a clever
example of a marketing memory lapse.

While they tout the ability for their hardware and software to scale,
they never mention that it'd take their $25K server and $100K SANS to do
it.  Not to mention the cost of the software itself.

Probably the primordial example of scaling is Google.  6000+ servers,
none of which (that I'm aware) are much more than nearly throw away i386
boxes.  And what language does most of it run?  Basic, old school, C
(although some Python/PHP is coming in house I hear).  This is a perfect
case where good architecture and design is what scaling is all about.

Or maybe their cost of scaling is measured in PhD's?

H