>>>>> On Thu, 23 Oct 2014 22:52:36 +0200, arjan tijms <arjan.tijms_at_gmail.com> said:
AT> This topic also came up a year ago on both the TomEE and Tomcat
AT> mailing lists (see
AT>
http://tomee-openejb.979440.n4.nabble.com/Consider-support-for-the-Servlet-profile-of-JSR-196-JASPIC-in-TomEE-td4660480.html
AT> and
http://tomcat.10.x6.nabble.com/Consider-support-for-the-Servlet-profile-of-JSR-196-JASPIC-in-Tomcat-7-0-x-td4993387.html).
AT> Responses there were fairly positive; with Mark and David eventually
AT> saying:
DB> If you wanted to roll up your sleeves, we'd be more than happy to
DB> see [Geronimo's JASPIC] ported or reimplemented in TomEE. or Tomcat
DB> :)
MT> That is taking what I said rather out of context.
MT> I recommend that folks read the entire discussion but the short
MT> version is that there is very, very little user demand for it. To
MT> date, Arjan is the only Tomcat user asking for JASPIC support in Tomcat.
This is one of those features that most people don't need, but when they
need it, they really really need it.
MT> Comparing this to WebSocket, we saw much, much more demand for
MT> WebSocket but no-one is talking about making WebSocket support
MT> mandatory for a Servlet container.
MT> I remain of the opinion that JASPIC support should be optional for a
MT> Servlet container.
Thanks for your definitive answer. Is there any circumstance where you
can imagine supporting it? It it a resource question? Is it an
architecture question? Is it because you feel JASPIC needs some
improvements first?
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| 5 work days til Devoxx 2014