tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Mast <>
Subject Re: FW: very off topic marketing question
Date Fri, 20 Mar 2009 23:53:08 GMT
>Meh. Most Java webapps aren't multithreaded anyway in the sense that
>each request lives in its own little world and usually runs start to
>finish with no other threading involved.

Just this week I added threading to a component of my web-app.  I had some
what dreaded it, but found that it took me only a half-hour and about 10
extra lines of code, here's a synopsis:

Thread t = new Thread(new Runnable() {
    public void run() {
}, "Blast Thread");


Where blast() iterates thru several thousand records, which are sent to a
third-party site for processing.  The third-party site allows no more than 5
connections per second, so I just call Thread.sleep(1000) on every 5th

It is very simple, very elegant and very fast now that some much load has
been moved off the main http thread.

My question is: how would this be accomplished in PHP?  Would I need to
recompile the whole php server with a special thread package or what?

On Fri, Mar 20, 2009 at 4:50 PM, Christopher Schultz <> wrote:

> Hash: SHA1
> Ilya,
> Don't get me wrong... I loves me some Java. But...
> On 3/20/2009 11:55 AM, Ilya Kazakevich wrote:
> > If you are going to move to php, be ready to:
> > 1) loose tools like log4j.
> log4p?
> > 2) meet API, 10% of which uses OOP and exceptions, and 90% is procedure /
> > errors based.
> This does really suck. It's going back and using C when you've become
> sooo used to exceptions.
> > 3) you would not have namespaces.
> Meh. I suppose on a large (huge?) project this could be a problem. You
> can always "namespace" your files by using subdirectories. Oh, wait. You
> weren't suggesting that you use objects in PHP were you? Ha ha ha ha.
> Oh, maybe you were. Sorry.
> > 4) because of dynamic typization, you would be able to find some types of
> > errors only in runtime.
> Java is not safe from runtime errors; they're just (mostly) not the
> kinds of errors that can be prevented using static type-checking. I've
> come-around on this one: static typing is just one way of doing things.
> Ruby's mix-ins are very attractive for those of us who have had trouble
> breaking-into a class hierarchy. :)
> > 5) no multithreading
> Meh. Most Java webapps aren't multithreaded anyway in the sense that
> each request lives in its own little world and usually runs start to
> finish with no other threading involved.
> - -chris
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla -
> UDgAn0eFpdBXzUCcda4G2LOE5733XSgL
> =X7eW
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message