Re: SEDA Future

Hi,
	You're right, X suffix is often used for eXtension and I think that this m=
ake=20
sense in this case.  Let me explain.

With our new seda3 implementation, I believe that the SEDA concept has=20
"evolved".  Indeed, a stage can now block to enqueue an event to another=20
stage and backpressure is managed automatically.  So, events cannot be lost=
=20
anymore.  This means that seda3 can be used for any kind of applications, n=
ot=20
only Internet services.  Thus, the scope of seda3 is much larger than SEDA.

This is why I see the actual seda3 design as a SEDA eXtension.

However, I totally agree to rename our core implementation (actually=20
Sandstorm) with another name, as JCyclone or other suggested names. =20

Cheers,
=2DJean



Le 29 Mars 2005 11:28, Quartz a =E9crit=A0:
> Hi,
>
> SEDA is an acronym. Sedax is a bit too close to that. I beleive that was a
> reason to call the project 'Sandstorm'. If you want to spin off sandstorm,
> You would be better advised to figure a cool name that doesn't refer to
> SEDA, especially not the X suffix conventionally used for standard
> extensions.
>
> May I suggest 'JCyclone', or something in the windy theme...
>
> --- [email protected] wrote:
> > Hi all,
> > 	Our web site is completly out of date.  Matt tell me that he would
> > prefer to keep the original SEDA site up and I understand that.
> >
> > So, we have decided to create a new project with another name.  This way
> > we can differentiate between the original SEDA project and the new.
> >
> > Note that the new project (SEDAX) is, and will be, based on the original
> > designs.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click