Re: ApplicationGateway vs DefaultEventGateway

On Tue, 2003-10-21 at 16:14, Diez B. Roggisch wrote:
> 
> We usually implement event-handlers as inner classes - so one big class 
> aggregate a great deal of inner classes. If you have a full fledged app, with 
> different parts like user management, content delivery, service center 
> application and so on, its preferable to seperate these parts into different 
> classes - a barracuda app is there no different than any other OO-based app. 
> Or do you stuff all your logic in one class ? :)

One shoot on hit ;) ... you're right.
 
> This might come more naturally if you used one class per event-handler - but I 
> plain hate the neccessity of one-file-one-class in java, and there isn't much 
> sense in creating dozens of useless declarative lines like imports when all 
> you want are two lines of code forwarding/handling an event.

Right again... also if this is much more like your taste but nothing to
say about that...

> But you might be right - its for displaying the capabilities. 
> 
> And before I compiled everything in one big, page-based example, the different 
[..]
> of mine.
> 

Thanks Diez for your work and your explanations...

--
Thelmo