rahul wrote:
>
> | Since the other apache modules case is still in the queue, I suggest
> | combining this one with it since it's more of the same (just 1 more
> | module). Saves the work of having separate cases.
>
> It would be nice to tackle dtrace separately as the work for others is
> already done (except for ARC) and they are waiting to be putback. I
> would rather not touch those if it is ok with you.
The case for the other modules has not been filed yet so there it no
gain in filing 2 cases at the same time for essentially the same
("more apache modules") thing.
> More over dtrace OSR has not been approved (and if the previous
> experience is any thing to go by it should take one or two months)
The OSR is approved (unfortunately not visible on the opensolaris site)...
> | List the exported probes in the exported interfaces. And from the
> | above, sounds like they are Volatile?
>
> This is more of a concern, perhaps we should wait until (either) it moves out
> of its alpha stage (or) one of us are willing to contribute to the
> developement (given that it is on solaris) and move it to stable land.
True, the options are to either not include the dtrace support at all
or add it as a Volatile interface for now until it is seen to
stabilize (there is a third option, which is to support it at a more
stable level at the risk of forking, but IMO we shouldn't consider
that, since we want to avoid any forks).
I think it'll be useful to include it as Volatile, since there is
interest in dtrace support for all components.
--
Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
