[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-dev] understanding the jetty 9.2.X architecture
|
I think Jetty will be quite dependant on what the underlying NIO has to
offer, as well functionality as performance.
The great thing about Jetty is that you will yourself be able to decide at
what point you take over.
As an example:
You could use a standard Jetty WebApp to serve out files and write only a
few lines of code. But Jetty allows you also to develop your own end-point
that deals itself with the file access (and possible your own application
specific optimized caching which is always more performant then standard
cash because it is tailored to the problem at hand - well, at least if you
know what you do :) .
In this last case your question is answered by yourself because you will
decide how you retrieve files from disk and cash them. Probably, if speed is
an issue, you will end up with NIO if you stick to standard Java Classes.
"Is there any document that explains the concepts above?"
I guess you are asking for a better Jetty Topology and Class positioning
discussion? I am interested in that myself because I would like to find out
which is the most performant set of classes to implement Async Jetty. See my
post of last week. I think only the developer on here that know Jetty inside
out will be able to provide that answer. I think Callback IO etc will be
part of the answer.
--
View this message in context: http://jetty.4.x6.nabble.com/jetty-dev-understanding-the-jetty-9-2-X-architecture-tp4962567p4962578.html
Sent from the Jetty Dev mailing list archive at Nabble.com.
