Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <20139112.post@talk.nabble.com>
Date: Thu, 23 Oct 2008 13:57:07 -0700 (PDT)
From: Kaj <kaj@finally.se>
To: camel-user@activemq.apache.org
Subject: Small API change suggestion, TimeUnit
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hi all,

I just went to Bruce Snyder's presentation on Camel at Software Summit. It
was a great session, and it looks like Camel is really great, but I saw that
something could be made a bit better :)

Some methods in the API takes a time value. The time value is in
milliseconds, and some of the methods are named something like fooMs, while
some others only are named foo. 

Knowing how much 24000 ms is isn't the easiest thing. Why not overload the
metods, or change the API so that the methods instead takes a TimeUnit and a
value as argument. E.g. TimeUnit.MINUTES, 5.

(I didn't know if I should have posted this in the user list or the
developer list so I posted it here).

Kaj


-- 
View this message in context: http://www.nabble.com/Small-API-change-suggestion%2C-TimeUnit-tp20139112s22882p20139112.html
Sent from the Camel - Users mailing list archive at Nabble.com.