Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of andythedestroyer@gmail.com
 designates 209.85.218.221 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=JoujnqU+XR5ZmEj344gtOxq1EsaN7FFRi7wEnWUU12N0ADGrh5CJ7PlkvBpdSA0eI1
         yEnAlO91Dzweo6Jn+UotMLyUMHgpI7qUAdiIyBcqnTp87z2ekHYxEz14l7a9Cauj7ZEi
         YGOcpcSbeUAr4kgPuJj5zyiWfgbSy43xtQ6Zo=
MIME-Version: 1.0
In-Reply-To: <fa2d9f450908100708x5272b03bx67263712a04c7b12@mail.gmail.com>
References: <8d32b3490908031212j6f80db18o7615f64c199b935a@mail.gmail.com>
	 <c7fc82820908050442j6e71d970j2cd2ace11a8a4f99@mail.gmail.com>
	 <8d32b3490908051211g19c5e6a6xc1ae0a57972fcb8d@mail.gmail.com>
	 <8d32b3490908061431g7ad6c1b0r7ea55733c0fd5db0@mail.gmail.com>
	 <fa2d9f450908070256p736b031et918b07bff5ac5697@mail.gmail.com>
	 <fa2d9f450908100708x5272b03bx67263712a04c7b12@mail.gmail.com>
Date: Mon, 10 Aug 2009 13:11:39 -0700
Message-ID: <8d32b3490908101311w13b9a02cy618d5a9e312a0950@mail.gmail.com>
Subject: Re: Stats code
From: Andy the destroyer <andythedestroyer@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=001636416a4d9676ee0470cf314a

--001636416a4d9676ee0470cf314a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

This is copied from Vassil's response another thread.

Vassil Dichev to esme-dev
show details 7:19 AM (5 hours ago)
Reply

[image: Follow up message]
> Latest code drop is deployed.

Ah, close miss for my latest minor fix :)

> Doesn't include andy's JMX code yet :-<  Haven't quite figured out how
> to do this was an elaborate cut and paste action.

>From command-line:

 patch -p0 < patch.diff

>From eclipse:

 Right-click on parent directory, Team -> Apply patch

The latest commits might have accumulated conflicts with the patch,
but shouldn't be difficult to do by hand for one or two conflicts. The
problem with Andy's code currently is that there's no public maven
repository where we can find Andy's modified library, where the bulk
of the code is.


..

That should work .. I can also commit my branch to my github account. You
could check it out there without having to worry about patchfiles.

Let me know..

-Andy

On Mon, Aug 10, 2009 at 7:08 AM, Richard Hirsch <hirsch.dick@gmail.com>wrote:

> I'd like to try out Andy's code but haven't figured out how do it
> without editing my way to insanity.
>
> Does someone else have some sort of a tool (SVN-related??) that takes
> a svn diff file and edits the source files to contain the changes?
>
> D.
>
> On Fri, Aug 7, 2009 at 11:56 AM, Richard Hirsch<hirsch.dick@gmail.com>
> wrote:
> > Thanks. I'll try and create a deployment based on the patch and deploy
> > it to Stax on Monday.
> >
> > D.
> >
> > On Thu, Aug 6, 2009 at 11:31 PM, Andy the
> > destroyer<andythedestroyer@gmail.com> wrote:
> >> I uploaded the patch and modified scala-stats.jar to JIRA (
> >> https://issues.apache.org/jira/browse/ESME-18).
> >>
> >> -Andy
> >>
> >> On Wed, Aug 5, 2009 at 12:11 PM, Andy the destroyer <
> >> andythedestroyer@gmail.com> wrote:
> >>
> >>> Hi Vassil,
> >>>
> >>> If you look at the scala-stats library, you need to look at my fork of
> it
> >>> on my git-hub account (http://github.com/andythedestroyer). I added
> some
> >>> more stats and JMX functionality that ESME is using. I provided a link
> note
> >>> in the pom section of the patch file. I am in contact with stevej it
> looks
> >>> like he is going to merge the changes I made into his master branch; I
> just
> >>> need to finish two more features and write the tests for them.
> >>>
> >>> I am also working on some actors for the scala-stats lib. I would be
> >>> interested to see your approach regarding stats and actors.
> >>>
> >>> I agree with you that retrieving stats with messages is a good idea. I
> even
> >>> started to look at what I would need to do to implement it. However,
> going
> >>> through the MsgParser was a nightmare. I am relatively new to Scala and
> very
> >>> new to parser combinators. With no comments in the code I found it very
> hard
> >>> to navigate my way through it and I moved on to other things.
> >>>
> >>> As far as licensing goes, scala-stats is under apache license and aside
> >>> from specs only has one dependecy-- configgy, which is also under
> Apache and
> >>> it's only dependecy is MarkdownJ which is BSD. Actually, the configgy
> dep is
> >>> optional. We don't even need it to run with ESME. Although, it might be
> >>> worth looking at configgy to manage ESME configs. Just a thought..
> >>>
> >>> I will submit the patch to the Jira ticket.
> >>>
> >>> Keep the faith,
> >>> Andy
> >>>
> >>>
> >>>
> >>> On Wed, Aug 5, 2009 at 4:42 AM, Vassil Dichev <vdichev@apache.org>
> wrote:
> >>>
> >>>> Thanks Andy, this looks like an efficient use of an external library.
> >>>> I just heard of stevej's library because it's used in Jonas Boner's
> >>>> new Akka actors library. I need to take a look into scala-stats and
> >>>> see what else we can use from this library.
> >>>>
> >>>> Incidentally, I'm also writing an actor for popularity stats- e.g.
> >>>> which messages have been resent the most in the last time period, or
> >>>> which links have been clicked the most, or which users have been using
> >>>> a certain tag/word, etc. The statistics from this actor should be
> >>>> available in a UI snippet for the user to see, but I see no reason
> >>>> that it shouldn't also be available via JMX.
> >>>>
> >>>> As an aside, we could also make an action in a way that we can emulate
> >>>> a JMX console bot within ESME. For instance, you write a message with
> >>>> text "stats usersLoggedIn" and you get back a message with the user
> >>>> count.
> >>>>
> >>>> I guess after trying the patch we need to check the licenses of the
> >>>> used scala-stats library *and* its dependencies (if any). I am not
> >>>> sure what the exact procedure is for accepting a patch- I think we
> >>>> need a JIRA item with an attached patch where you click a license
> >>>> agreement.
> >>>>
> >>>> Thanks again, it's nice to see find ESME fun to work on!
> >>>>
> >>>> Vassil
> >>>>
> >>>
> >>>
> >>
> >
>

--001636416a4d9676ee0470cf314a--