You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Jack Park <ja...@topicquests.org> on 2011/09/01 22:54:04 UTC
Re: 1.4 planning
Somewhat beyond 1.4, I'd like to ask about persistence other than RDBMS.
For instance, in microblogging, there is some evidence that Redis can
provide a scalable datastore.
Thoughts?
Cheers
Jack
On 8/29/2011 11:27 PM, Richard Hirsch wrote:
> I've been thinking about the next release and wanted to start
> collecting ideas for features for this release.
>
> There are some tasks in Jira [1] but that list isn't complete:
>
> Here are some other ideas:
>
> * Integration with Akka / Apache Camel
> * Simplification of URLs
> * Change Web UI to deal with new icon
>
> Any one else have other ideas / suggestions?
>
> D.
>
> [1] https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ESME+AND+fixVersion+%3D+%221.4%22+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
Re: 1.4 planning
Posted by Richard Hirsch <hi...@gmail.com>.
@Jack - I've created a JIRA item for it:
https://issues.apache.org/jira/browse/ESME-358. I set the version to
1.4 and backlog.
If you create a user for yourself in JIRA, I'll assign you to it.
D.
On Mon, Sep 5, 2011 at 10:11 PM, Jack Park <ja...@topicquests.org> wrote:
> I started with https://github.com/indrajitr/scala-redis
> and, thanks to conversations with Indrajit, have learned that I can craft
> what I call RedisModel (an object) that holds a live instance of RedisClient
> and presents a useful API for doing timelines and nodes. I'm working on that
> now. RedisClient must be configured in Boot.scala
Re: 1.4 planning
Posted by Vladimir Ivanov <le...@gmail.com>.
Hi Jack,
Ok, I take your point. Thanks for the explanations.
Vladimir
2011/9/13 Jack Park <ja...@topicquests.org>
> Hi Vladimir,
>
> I am using Indrajit's scala library, not in ESME, but in another project
> project that is a precursor to features I want to later add to ESME.
>
> I am not able to say with any certainty that Lift's Record API doesn't fit
> well; I started to think about it by sketching two implementations, one for
> documents (ESME nodes, pure get/put key-value pairs where the value is a
> JSON representation of the node) and one for timelines (the Redis List
> structure), then decided, perhaps if for no other reason than gross
> simplicity, to go with simply using the Redis API directly. I'll offer this
> hunch: Record extensions can, and perhaps should be implemented for ESME
> nodes and for timelines. For now, I'm not going that direction but don't
> rule it out in the future.
>
> I, too, am looking forward to seeing the results ;-)
>
> Jack
>
>
> On 9/13/2011 9:28 AM, Vladimir Ivanov wrote:
>
>> Hi Jack!
>>
>> Your thoughts regarding Redis integration seem very interesting.
>> Unfortunately I haven't had time to look closer into it. As I understood
>> from your comment - Lift's Record API doesn't fit well with Redis? Are you
>> going to use indrajitr's scala library for Redis?
>>
>> I'm looking forward to see the results!
>>
>> Vladimir
>>
>>
>> 2011/9/6 Jack Park<ja...@topicquests.org>
>>
>> At the moment, I'm not sure about creating a Jira for it, but I am
>>> working
>>> on it. I started with https://github.com/indrajitr/****scala-redis<https://github.com/indrajitr/**scala-redis>
>>> <https://github.**com/indrajitr/scala-redis<https://github.com/indrajitr/scala-redis>
>>> >
>>>
>>> and, thanks to conversations with Indrajit, have learned that I can craft
>>> what I call RedisModel (an object) that holds a live instance of
>>> RedisClient
>>> and presents a useful API for doing timelines and nodes. I'm working on
>>> that
>>> now. RedisClient must be configured in Boot.scala
>>>
>>> When I get something that works, I'll toss it up to github and ask others
>>> to polish the work of this scala beginner.
>>>
>>> My present thinking is that user modeling is still handled in an RDBMS
>>> (though, I suppose, even there it's possible to run into scaling
>>> problems)
>>>
>>> Jack
>>>
>>>
>>> On 9/2/2011 10:25 AM, Ethan Jewett wrote:
>>>
>>> That's a good point. Nothing with that level of scale is currently in
>>>> the realm of possibility for our use-cases, but as machine-generated
>>>> data becomes more prevalent it is going to become more of a problem.
>>>>
>>>> Want to create a Jira for it and assign it to the backlog? If you have
>>>> some ideas about how this should be done or want to work on a
>>>> prototype, go for it :-)
>>>>
>>>> Ethan
>>>>
>>>> On Fri, Sep 2, 2011 at 6:07 PM, Jack Park<ja...@topicquests.org>
>>>> wrote:
>>>>
>>>> The interesting question for me is: how many records can you store in
>>>>> an
>>>>> RDBMS before you have to think about scale up issues? I wrote a trivial
>>>>> microblog in Java using Redis; I think there is a candidate fit.
>>>>>
>>>>> Cheers
>>>>> Jack
>>>>>
>>>>> On 9/1/2011 11:53 PM, Ethan Jewett wrote:
>>>>>
>>>>>
>>>>>> It's certainly an interesting idea, and Lift does have some built-in
>>>>>> capabilities here in the form of the Record module. It would be a
>>>>>> pretty significant migration.
>>>>>>
>>>>>> An interesting question to explore: Would this give us a performance
>>>>>> boost in some scenarios?
>>>>>>
>>>>>> Cheers,
>>>>>> Ethan
>>>>>>
>>>>>> On Thu, Sep 1, 2011 at 10:54 PM, Jack Park<ja...@topicquests.org>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>> Somewhat beyond 1.4, I'd like to ask about persistence other than
>>>>>>> RDBMS.
>>>>>>> For
>>>>>>> instance, in microblogging, there is some evidence that Redis can
>>>>>>> provide
>>>>>>> a
>>>>>>> scalable datastore.
>>>>>>>
>>>>>>> Thoughts?
>>>>>>>
>>>>>>> Cheers
>>>>>>> Jack
>>>>>>>
>>>>>>> On 8/29/2011 11:27 PM, Richard Hirsch wrote:
>>>>>>>
>>>>>>>
>>>>>>>> I've been thinking about the next release and wanted to start
>>>>>>>> collecting ideas for features for this release.
>>>>>>>>
>>>>>>>> There are some tasks in Jira [1] but that list isn't complete:
>>>>>>>>
>>>>>>>> Here are some other ideas:
>>>>>>>>
>>>>>>>> * Integration with Akka / Apache Camel
>>>>>>>> * Simplification of URLs
>>>>>>>> * Change Web UI to deal with new icon
>>>>>>>>
>>>>>>>> Any one else have other ideas / suggestions?
>>>>>>>>
>>>>>>>> D.
>>>>>>>>
>>>>>>>> [1]
>>>>>>>>
>>>>>>>> https://issues.apache.org/****jira/secure/IssueNavigator.**<https://issues.apache.org/**jira/secure/IssueNavigator.**>
>>>>>>>> jspa?reset=true&jqlQuery=****project+%3D+ESME+AND+**
>>>>>>>> fixVersion+%3D+%221.4%22+AND+****status+%3D+Open+ORDER+BY+**
>>>>>>>> priority+DESC&mode=hide<https:**//issues.apache.org/jira/**
>>>>>>>> secure/IssueNavigator.jspa?**reset=true&jqlQuery=project+%**
>>>>>>>> 3D+ESME+AND+fixVersion+%3D+%**221.4%22+AND+status+%3D+Open+**
>>>>>>>> ORDER+BY+priority+DESC&mode=**hide<https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ESME+AND+fixVersion+%3D+%221.4%22+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide>
>>>>>>>> >
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>
>>
--
Best Regards,
Vladimir Ivanov
Re: Compiling 1.3 observations
Posted by Ethan Jewett <es...@gmail.com>.
We need to fix the test failures. Regarding the compilation warnings,
we have an issue open for this one :-)
https://issues.apache.org/jira/browse/ESME-362
Cheers,
Ethan
On Fri, Sep 23, 2011 at 7:06 AM, Jack Park <ja...@topicquests.org> wrote:
> I built the 1.3 distro with maven (comments below), and unbundled the war
> int a Jetty ROOT directory. It's running fine. Will exercise its
> capabilities soon. Meanwhile, here are some observations from the build.
>
> Jack
>
> Running mvn install
> These warnings
> [WARNING]
> C:\projects\SCALA-Projects\ESME\1.3\apache-esme-1.3\server\src\main\sc
> ala\org\apache\esme\model\UserAuth.scala:384: warning: match is not
> exhaustive!
> [WARNING] missing combination Failure
> [WARNING] missing combination ParamFailure
> [WARNING]
> [WARNING] S.request match {
> [WARNING] ^
> [WARNING]
> C:\projects\SCALA-Projects\ESME\1.3\apache-esme-1.3\server\src\main\sc
> ala\org\apache\esme\model\UserAuth.scala:468: warning: match is not
> exhaustive!
> [WARNING] missing combination Failure
> [WARNING] missing combination ParamFailure
> [WARNING]
> [WARNING] user <- UserAuth.find(By(UserAuth.authKey, name),
> [WARNING] ^
>
> test issues
> Running org.apache.esme.actor.PopStatsActorSpecsAsTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.442 sec
> <<< FA
> ILURE!
> Running org.apache.esme.api.Api2SpecsAsTest
> log4j:WARN No appenders could be found for logger (org.mortbay.log).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
> more in
> fo.
> INF [20110922-21:47:51.783] ostrich: Starting TimeSeriesCollector
> :12:209: '/' expected instead of ' '
>
>
>
> ^
> :12:209: '/' expected instead of ' '
>
>
>
> ^
> Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 57.512 sec
> Running org.apache.esme.api.ApiSpecsAsTest
> Full(<esme_api success="true"
> operation="send_msg"><xml:group></xml:group></esme
> _api>)
> Full(<esme_api msg="message parameter is missing" success="false"
> operation="sen
> d_msg"><xml:group></xml:group></esme_api>)
> Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.277 sec
> Running org.apache.esme.api.TwitterAPISpecsAsTest
> :12:209: '/' expected instead of ' '
>
>
Re: User interface observations
Posted by Jack Park <ja...@topicquests.org>.
Continuing the saga: Joe creates a tag while in a shared pool. Joe sees
the tag. It does not show up in the views of others, including when the
pool, itself, is selected. Are tags not public objects visible to all?
The tag *is* in the message viewed in the pool to others, just not in
the tag cloud.
Thanks in advance (still learning)
Jack
On 9/24/2011 10:38 AM, Jack Park wrote:
> Everything I'm reporting is from the perspective of a naive user; no
> deep thinking is engaged. Thus, for instance, not realizing I would need
> to refresh the pool view in order to pick up a new user that came online
> while that view is still bound internally, provoked a bug report that's
> not a bug at all.
>
> Now, I am happy to report that Joe is a member of my pool; Joe sent a
> message to that pool. The number of exploratory gestures necessary to
> see that message in my pool is the subject of this observation.
>
> I ended up having to look at Streams.
> Then I ended up having to select my pool in that stream. But, that's not
> enough. I had to turn on a check box that says something about pool
> filters.
>
> I'm guessing that, over time, I'll recognize just how powerful those
> sequences really are; just reporting that they did not come from any
> intuitions about the user interface. Not even complaining, just
> observing, wondering how else to get there from here...
>
> Jack
User interface observations
Posted by Jack Park <ja...@topicquests.org>.
Everything I'm reporting is from the perspective of a naive user; no
deep thinking is engaged. Thus, for instance, not realizing I would need
to refresh the pool view in order to pick up a new user that came online
while that view is still bound internally, provoked a bug report that's
not a bug at all.
Now, I am happy to report that Joe is a member of my pool; Joe sent a
message to that pool. The number of exploratory gestures necessary to
see that message in my pool is the subject of this observation.
I ended up having to look at Streams.
Then I ended up having to select my pool in that stream. But, that's not
enough. I had to turn on a check box that says something about pool filters.
I'm guessing that, over time, I'll recognize just how powerful those
sequences really are; just reporting that they did not come from any
intuitions about the user interface. Not even complaining, just
observing, wondering how else to get there from here...
Jack
Re: Compiling 1.3 observations
Posted by Jack Park <ja...@topicquests.org>.
Clear the cache, Luke!
That hit me as I woke up this morning. In fact, it's working fine on FF
now. One has to wonder: how is it that Chrome and IE do the right
thing, but FF is willing to reuse a bad file...
Dopey me!
Cheers
Jack
On 9/22/2011 10:44 PM, Richard Hirsch wrote:
> @Jack Thanks for the info. . Let me test on FireFox. I just tested on
> Chrome and IE.
>
> D.
>
>
>
> On Fri, Sep 23, 2011 at 7:17 AM, Jack Park<ja...@topicquests.org> wrote:
>> A first observation of runtime:
>>
>> Appearance is as expected in Chrome and IE
>> Appearance in Firefox 6.0.2 on Win7 is such that it's clear that CSS is not
>> being followed. Nothing is in place, all styling is missing. In fact, the
>> "Public"link to switch the landing page to see all messages is missing.
>>
>> Jack
>>
>> On 9/22/2011 10:06 PM, Jack Park wrote:
>>>
>>> I built the 1.3 distro with maven (comments below), and unbundled the
>>> war int a Jetty ROOT directory. It's running fine. Will exercise its
>>> capabilities soon. Meanwhile, here are some observations from the build.
>>>
>>> Jack
>>>
>>> Running mvn install
>>> These warnings
>>> [WARNING]
>>> C:\projects\SCALA-Projects\ESME\1.3\apache-esme-1.3\server\src\main\sc
>>> ala\org\apache\esme\model\UserAuth.scala:384: warning: match is not
>>> exhaustive!
>>> [WARNING] missing combination Failure
>>> [WARNING] missing combination ParamFailure
>>> [WARNING]
>>> [WARNING] S.request match {
>>> [WARNING] ^
>>> [WARNING]
>>> C:\projects\SCALA-Projects\ESME\1.3\apache-esme-1.3\server\src\main\sc
>>> ala\org\apache\esme\model\UserAuth.scala:468: warning: match is not
>>> exhaustive!
>>> [WARNING] missing combination Failure
>>> [WARNING] missing combination ParamFailure
>>> [WARNING]
>>> [WARNING] user<- UserAuth.find(By(UserAuth.authKey, name),
>>> [WARNING] ^
>>>
>>> test issues
>>> Running org.apache.esme.actor.PopStatsActorSpecsAsTest
>>> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.442
>>> sec<<< FA
>>> ILURE!
>>> Running org.apache.esme.api.Api2SpecsAsTest
>>> log4j:WARN No appenders could be found for logger (org.mortbay.log).
>>> log4j:WARN Please initialize the log4j system properly.
>>> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
>>> more in
>>> fo.
>>> INF [20110922-21:47:51.783] ostrich: Starting TimeSeriesCollector
>>> :12:209: '/' expected instead of ' '
>>>
>>>
>>>
>>> ^
>>> :12:209: '/' expected instead of ' '
>>>
>>>
>>>
>>> ^
>>> Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 57.512
>>> sec
>>> Running org.apache.esme.api.ApiSpecsAsTest
>>> Full(<esme_api success="true"
>>> operation="send_msg"><xml:group></xml:group></esme
>>> _api>)
>>> Full(<esme_api msg="message parameter is missing" success="false"
>>> operation="sen
>>> d_msg"><xml:group></xml:group></esme_api>)
>>> Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.277 sec
>>> Running org.apache.esme.api.TwitterAPISpecsAsTest
>>> :12:209: '/' expected instead of ' '
>>>
>>
Re: Compiling 1.3 observations
Posted by Richard Hirsch <hi...@gmail.com>.
@Jack Thanks for the info. . Let me test on FireFox. I just tested on
Chrome and IE.
D.
On Fri, Sep 23, 2011 at 7:17 AM, Jack Park <ja...@topicquests.org> wrote:
> A first observation of runtime:
>
> Appearance is as expected in Chrome and IE
> Appearance in Firefox 6.0.2 on Win7 is such that it's clear that CSS is not
> being followed. Nothing is in place, all styling is missing. In fact, the
> "Public"link to switch the landing page to see all messages is missing.
>
> Jack
>
> On 9/22/2011 10:06 PM, Jack Park wrote:
>>
>> I built the 1.3 distro with maven (comments below), and unbundled the
>> war int a Jetty ROOT directory. It's running fine. Will exercise its
>> capabilities soon. Meanwhile, here are some observations from the build.
>>
>> Jack
>>
>> Running mvn install
>> These warnings
>> [WARNING]
>> C:\projects\SCALA-Projects\ESME\1.3\apache-esme-1.3\server\src\main\sc
>> ala\org\apache\esme\model\UserAuth.scala:384: warning: match is not
>> exhaustive!
>> [WARNING] missing combination Failure
>> [WARNING] missing combination ParamFailure
>> [WARNING]
>> [WARNING] S.request match {
>> [WARNING] ^
>> [WARNING]
>> C:\projects\SCALA-Projects\ESME\1.3\apache-esme-1.3\server\src\main\sc
>> ala\org\apache\esme\model\UserAuth.scala:468: warning: match is not
>> exhaustive!
>> [WARNING] missing combination Failure
>> [WARNING] missing combination ParamFailure
>> [WARNING]
>> [WARNING] user <- UserAuth.find(By(UserAuth.authKey, name),
>> [WARNING] ^
>>
>> test issues
>> Running org.apache.esme.actor.PopStatsActorSpecsAsTest
>> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.442
>> sec <<< FA
>> ILURE!
>> Running org.apache.esme.api.Api2SpecsAsTest
>> log4j:WARN No appenders could be found for logger (org.mortbay.log).
>> log4j:WARN Please initialize the log4j system properly.
>> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
>> more in
>> fo.
>> INF [20110922-21:47:51.783] ostrich: Starting TimeSeriesCollector
>> :12:209: '/' expected instead of ' '
>>
>>
>>
>> ^
>> :12:209: '/' expected instead of ' '
>>
>>
>>
>> ^
>> Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 57.512
>> sec
>> Running org.apache.esme.api.ApiSpecsAsTest
>> Full(<esme_api success="true"
>> operation="send_msg"><xml:group></xml:group></esme
>> _api>)
>> Full(<esme_api msg="message parameter is missing" success="false"
>> operation="sen
>> d_msg"><xml:group></xml:group></esme_api>)
>> Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.277 sec
>> Running org.apache.esme.api.TwitterAPISpecsAsTest
>> :12:209: '/' expected instead of ' '
>>
>
Re: First running 1.3 observations
Posted by Jack Park <ja...@topicquests.org>.
Issue added to Jira.
Yes, I did not expect Joe to see it, unless it had been created but not
showing.
Jack
On 9/23/2011 12:06 AM, Ethan Jewett wrote:
> Hi Jack,
>
> Thanks for the feedback and for finding this bug. Comments are inline:
>
> On Fri, Sep 23, 2011 at 7:40 AM, Jack Park<ja...@topicquests.org> wrote:
>> I created a pool.
>> In another browser (IE), I created another user, "joe", and made some posts.
>> Then, went back to my account and tried to add "joe" into my pool. (The
>> "Edit" button is someone misleading). I can type in joe for the user, and
>> give him either a Read or Write role. Click Add User button. Nothing
>> happens. No "joe" in the list of users. Tried his full name "Joe Sixpack"
>> -- it really didn't like that, and still refused to accept "joe", not even
>> giving an error message.
>
> This is a bug where the list of users in the pool isn't updating after
> adding a user. If you reload the page and reselect the pool, you'll
> see "joe" in the list, I think. Can you create a Jira issue for this?
>
> Aside from that, we clearly need to do some work on the usability of
> the pool management interface. It has been pretty confusing since the
> beginning. Would be worth having a Jira issue for this too!
>
> If you don't get to creating the issues, I'm sure either Dick or I
> will get to it this weekend.
>
>> Joe is unable to "see" my pool in his browser.
>
> Joe won't see messages that were posted to the pool before he was
> added to the pool. Try posting a new message to the pool and see if
> Joe sees it. If you added Joe with a Write role, he should also be
> able to see the pool in the "Share with" dropdown when composing a
> message.
>
>> Perhaps I'm missing something; just doing what seems intuitive.
>
> I think it's not very intuitive at the moment, which is definitely a problem.
>
> Cheers,
> Ethan
>
>>
>> Jack
>>
>> On 9/22/2011 10:17 PM, Jack Park wrote:
>>>
>>> A first observation of runtime:
>>>
>>> Appearance is as expected in Chrome and IE
>>> Appearance in Firefox 6.0.2 on Win7 is such that it's clear that CSS is
>>> not being followed. Nothing is in place, all styling is missing. In
>>> fact, the "Public"link to switch the landing page to see all messages is
>>> missing.
>>>
>>> Jack
>>>
>>
Re: First running 1.3 observations
Posted by Richard Hirsch <hi...@gmail.com>.
We (I) should probably surface more of our ideas about pools on the
CMS site. Actually, there is quite a bit of documentation present but
it is either hidden in the mail archives or in the old wiki.
I'll put in on my list to surface this information.
D.
On Fri, Sep 23, 2011 at 9:06 AM, Ethan Jewett <es...@gmail.com> wrote:
> Hi Jack,
>
> Thanks for the feedback and for finding this bug. Comments are inline:
>
> On Fri, Sep 23, 2011 at 7:40 AM, Jack Park <ja...@topicquests.org> wrote:
>> I created a pool.
>> In another browser (IE), I created another user, "joe", and made some posts.
>> Then, went back to my account and tried to add "joe" into my pool. (The
>> "Edit" button is someone misleading). I can type in joe for the user, and
>> give him either a Read or Write role. Click Add User button. Nothing
>> happens. No "joe" in the list of users. Tried his full name "Joe Sixpack"
>> -- it really didn't like that, and still refused to accept "joe", not even
>> giving an error message.
>
> This is a bug where the list of users in the pool isn't updating after
> adding a user. If you reload the page and reselect the pool, you'll
> see "joe" in the list, I think. Can you create a Jira issue for this?
>
> Aside from that, we clearly need to do some work on the usability of
> the pool management interface. It has been pretty confusing since the
> beginning. Would be worth having a Jira issue for this too!
>
> If you don't get to creating the issues, I'm sure either Dick or I
> will get to it this weekend.
>
>> Joe is unable to "see" my pool in his browser.
>
> Joe won't see messages that were posted to the pool before he was
> added to the pool. Try posting a new message to the pool and see if
> Joe sees it. If you added Joe with a Write role, he should also be
> able to see the pool in the "Share with" dropdown when composing a
> message.
>
>> Perhaps I'm missing something; just doing what seems intuitive.
>
> I think it's not very intuitive at the moment, which is definitely a problem.
>
> Cheers,
> Ethan
>
>>
>> Jack
>>
>> On 9/22/2011 10:17 PM, Jack Park wrote:
>>>
>>> A first observation of runtime:
>>>
>>> Appearance is as expected in Chrome and IE
>>> Appearance in Firefox 6.0.2 on Win7 is such that it's clear that CSS is
>>> not being followed. Nothing is in place, all styling is missing. In
>>> fact, the "Public"link to switch the landing page to see all messages is
>>> missing.
>>>
>>> Jack
>>>
>>
>
Re: First running 1.3 observations
Posted by Ethan Jewett <es...@gmail.com>.
Hi Jack,
Thanks for the feedback and for finding this bug. Comments are inline:
On Fri, Sep 23, 2011 at 7:40 AM, Jack Park <ja...@topicquests.org> wrote:
> I created a pool.
> In another browser (IE), I created another user, "joe", and made some posts.
> Then, went back to my account and tried to add "joe" into my pool. (The
> "Edit" button is someone misleading). I can type in joe for the user, and
> give him either a Read or Write role. Click Add User button. Nothing
> happens. No "joe" in the list of users. Tried his full name "Joe Sixpack"
> -- it really didn't like that, and still refused to accept "joe", not even
> giving an error message.
This is a bug where the list of users in the pool isn't updating after
adding a user. If you reload the page and reselect the pool, you'll
see "joe" in the list, I think. Can you create a Jira issue for this?
Aside from that, we clearly need to do some work on the usability of
the pool management interface. It has been pretty confusing since the
beginning. Would be worth having a Jira issue for this too!
If you don't get to creating the issues, I'm sure either Dick or I
will get to it this weekend.
> Joe is unable to "see" my pool in his browser.
Joe won't see messages that were posted to the pool before he was
added to the pool. Try posting a new message to the pool and see if
Joe sees it. If you added Joe with a Write role, he should also be
able to see the pool in the "Share with" dropdown when composing a
message.
> Perhaps I'm missing something; just doing what seems intuitive.
I think it's not very intuitive at the moment, which is definitely a problem.
Cheers,
Ethan
>
> Jack
>
> On 9/22/2011 10:17 PM, Jack Park wrote:
>>
>> A first observation of runtime:
>>
>> Appearance is as expected in Chrome and IE
>> Appearance in Firefox 6.0.2 on Win7 is such that it's clear that CSS is
>> not being followed. Nothing is in place, all styling is missing. In
>> fact, the "Public"link to switch the landing page to see all messages is
>> missing.
>>
>> Jack
>>
>
First running 1.3 observations
Posted by Jack Park <ja...@topicquests.org>.
Now that it's running, aside from a CSS issue with Firefox mentioned
below, it's being confusing in relation to pools.
I created a pool.
In another browser (IE), I created another user, "joe", and made some
posts. Then, went back to my account and tried to add "joe" into my
pool. (The "Edit" button is someone misleading). I can type in joe for
the user, and give him either a Read or Write role. Click Add User
button. Nothing happens. No "joe" in the list of users. Tried his full
name "Joe Sixpack" -- it really didn't like that, and still refused to
accept "joe", not even giving an error message.
Joe is unable to "see" my pool in his browser.
Perhaps I'm missing something; just doing what seems intuitive.
Jack
On 9/22/2011 10:17 PM, Jack Park wrote:
> A first observation of runtime:
>
> Appearance is as expected in Chrome and IE
> Appearance in Firefox 6.0.2 on Win7 is such that it's clear that CSS is
> not being followed. Nothing is in place, all styling is missing. In
> fact, the "Public"link to switch the landing page to see all messages is
> missing.
>
> Jack
>
Re: Compiling 1.3 observations
Posted by Jack Park <ja...@topicquests.org>.
A first observation of runtime:
Appearance is as expected in Chrome and IE
Appearance in Firefox 6.0.2 on Win7 is such that it's clear that CSS is
not being followed. Nothing is in place, all styling is missing. In
fact, the "Public"link to switch the landing page to see all messages is
missing.
Jack
On 9/22/2011 10:06 PM, Jack Park wrote:
> I built the 1.3 distro with maven (comments below), and unbundled the
> war int a Jetty ROOT directory. It's running fine. Will exercise its
> capabilities soon. Meanwhile, here are some observations from the build.
>
> Jack
>
> Running mvn install
> These warnings
> [WARNING]
> C:\projects\SCALA-Projects\ESME\1.3\apache-esme-1.3\server\src\main\sc
> ala\org\apache\esme\model\UserAuth.scala:384: warning: match is not
> exhaustive!
> [WARNING] missing combination Failure
> [WARNING] missing combination ParamFailure
> [WARNING]
> [WARNING] S.request match {
> [WARNING] ^
> [WARNING]
> C:\projects\SCALA-Projects\ESME\1.3\apache-esme-1.3\server\src\main\sc
> ala\org\apache\esme\model\UserAuth.scala:468: warning: match is not
> exhaustive!
> [WARNING] missing combination Failure
> [WARNING] missing combination ParamFailure
> [WARNING]
> [WARNING] user <- UserAuth.find(By(UserAuth.authKey, name),
> [WARNING] ^
>
> test issues
> Running org.apache.esme.actor.PopStatsActorSpecsAsTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.442
> sec <<< FA
> ILURE!
> Running org.apache.esme.api.Api2SpecsAsTest
> log4j:WARN No appenders could be found for logger (org.mortbay.log).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
> more in
> fo.
> INF [20110922-21:47:51.783] ostrich: Starting TimeSeriesCollector
> :12:209: '/' expected instead of ' '
>
>
>
> ^
> :12:209: '/' expected instead of ' '
>
>
>
> ^
> Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 57.512 sec
> Running org.apache.esme.api.ApiSpecsAsTest
> Full(<esme_api success="true"
> operation="send_msg"><xml:group></xml:group></esme
> _api>)
> Full(<esme_api msg="message parameter is missing" success="false"
> operation="sen
> d_msg"><xml:group></xml:group></esme_api>)
> Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.277 sec
> Running org.apache.esme.api.TwitterAPISpecsAsTest
> :12:209: '/' expected instead of ' '
>
Compiling 1.3 observations
Posted by Jack Park <ja...@topicquests.org>.
I built the 1.3 distro with maven (comments below), and unbundled the
war int a Jetty ROOT directory. It's running fine. Will exercise its
capabilities soon. Meanwhile, here are some observations from the build.
Jack
Running mvn install
These warnings
[WARNING]
C:\projects\SCALA-Projects\ESME\1.3\apache-esme-1.3\server\src\main\sc
ala\org\apache\esme\model\UserAuth.scala:384: warning: match is not
exhaustive!
[WARNING] missing combination Failure
[WARNING] missing combination ParamFailure
[WARNING]
[WARNING] S.request match {
[WARNING] ^
[WARNING]
C:\projects\SCALA-Projects\ESME\1.3\apache-esme-1.3\server\src\main\sc
ala\org\apache\esme\model\UserAuth.scala:468: warning: match is not
exhaustive!
[WARNING] missing combination Failure
[WARNING] missing combination ParamFailure
[WARNING]
[WARNING] user <- UserAuth.find(By(UserAuth.authKey, name),
[WARNING] ^
test issues
Running org.apache.esme.actor.PopStatsActorSpecsAsTest
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.442
sec <<< FA
ILURE!
Running org.apache.esme.api.Api2SpecsAsTest
log4j:WARN No appenders could be found for logger (org.mortbay.log).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more in
fo.
INF [20110922-21:47:51.783] ostrich: Starting TimeSeriesCollector
:12:209: '/' expected instead of ' '
^
:12:209: '/' expected instead of ' '
^
Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 57.512 sec
Running org.apache.esme.api.ApiSpecsAsTest
Full(<esme_api success="true"
operation="send_msg"><xml:group></xml:group></esme
_api>)
Full(<esme_api msg="message parameter is missing" success="false"
operation="sen
d_msg"><xml:group></xml:group></esme_api>)
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.277 sec
Running org.apache.esme.api.TwitterAPISpecsAsTest
:12:209: '/' expected instead of ' '
Re: 1.4 planning
Posted by Jack Park <ja...@topicquests.org>.
Hi Vladimir,
I am using Indrajit's scala library, not in ESME, but in another project
project that is a precursor to features I want to later add to ESME.
I am not able to say with any certainty that Lift's Record API doesn't
fit well; I started to think about it by sketching two implementations,
one for documents (ESME nodes, pure get/put key-value pairs where the
value is a JSON representation of the node) and one for timelines (the
Redis List structure), then decided, perhaps if for no other reason than
gross simplicity, to go with simply using the Redis API directly. I'll
offer this hunch: Record extensions can, and perhaps should be
implemented for ESME nodes and for timelines. For now, I'm not going
that direction but don't rule it out in the future.
I, too, am looking forward to seeing the results ;-)
Jack
On 9/13/2011 9:28 AM, Vladimir Ivanov wrote:
> Hi Jack!
>
> Your thoughts regarding Redis integration seem very interesting.
> Unfortunately I haven't had time to look closer into it. As I understood
> from your comment - Lift's Record API doesn't fit well with Redis? Are you
> going to use indrajitr's scala library for Redis?
>
> I'm looking forward to see the results!
>
> Vladimir
>
>
> 2011/9/6 Jack Park<ja...@topicquests.org>
>
>> At the moment, I'm not sure about creating a Jira for it, but I am working
>> on it. I started with https://github.com/indrajitr/**scala-redis<https://github.com/indrajitr/scala-redis>
>> and, thanks to conversations with Indrajit, have learned that I can craft
>> what I call RedisModel (an object) that holds a live instance of RedisClient
>> and presents a useful API for doing timelines and nodes. I'm working on that
>> now. RedisClient must be configured in Boot.scala
>>
>> When I get something that works, I'll toss it up to github and ask others
>> to polish the work of this scala beginner.
>>
>> My present thinking is that user modeling is still handled in an RDBMS
>> (though, I suppose, even there it's possible to run into scaling problems)
>>
>> Jack
>>
>>
>> On 9/2/2011 10:25 AM, Ethan Jewett wrote:
>>
>>> That's a good point. Nothing with that level of scale is currently in
>>> the realm of possibility for our use-cases, but as machine-generated
>>> data becomes more prevalent it is going to become more of a problem.
>>>
>>> Want to create a Jira for it and assign it to the backlog? If you have
>>> some ideas about how this should be done or want to work on a
>>> prototype, go for it :-)
>>>
>>> Ethan
>>>
>>> On Fri, Sep 2, 2011 at 6:07 PM, Jack Park<ja...@topicquests.org>
>>> wrote:
>>>
>>>> The interesting question for me is: how many records can you store in an
>>>> RDBMS before you have to think about scale up issues? I wrote a trivial
>>>> microblog in Java using Redis; I think there is a candidate fit.
>>>>
>>>> Cheers
>>>> Jack
>>>>
>>>> On 9/1/2011 11:53 PM, Ethan Jewett wrote:
>>>>
>>>>>
>>>>> It's certainly an interesting idea, and Lift does have some built-in
>>>>> capabilities here in the form of the Record module. It would be a
>>>>> pretty significant migration.
>>>>>
>>>>> An interesting question to explore: Would this give us a performance
>>>>> boost in some scenarios?
>>>>>
>>>>> Cheers,
>>>>> Ethan
>>>>>
>>>>> On Thu, Sep 1, 2011 at 10:54 PM, Jack Park<ja...@topicquests.org>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> Somewhat beyond 1.4, I'd like to ask about persistence other than
>>>>>> RDBMS.
>>>>>> For
>>>>>> instance, in microblogging, there is some evidence that Redis can
>>>>>> provide
>>>>>> a
>>>>>> scalable datastore.
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> Cheers
>>>>>> Jack
>>>>>>
>>>>>> On 8/29/2011 11:27 PM, Richard Hirsch wrote:
>>>>>>
>>>>>>>
>>>>>>> I've been thinking about the next release and wanted to start
>>>>>>> collecting ideas for features for this release.
>>>>>>>
>>>>>>> There are some tasks in Jira [1] but that list isn't complete:
>>>>>>>
>>>>>>> Here are some other ideas:
>>>>>>>
>>>>>>> * Integration with Akka / Apache Camel
>>>>>>> * Simplification of URLs
>>>>>>> * Change Web UI to deal with new icon
>>>>>>>
>>>>>>> Any one else have other ideas / suggestions?
>>>>>>>
>>>>>>> D.
>>>>>>>
>>>>>>> [1]
>>>>>>>
>>>>>>> https://issues.apache.org/**jira/secure/IssueNavigator.**
>>>>>>> jspa?reset=true&jqlQuery=**project+%3D+ESME+AND+**
>>>>>>> fixVersion+%3D+%221.4%22+AND+**status+%3D+Open+ORDER+BY+**
>>>>>>> priority+DESC&mode=hide<https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ESME+AND+fixVersion+%3D+%221.4%22+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>
>
Re: 1.4 planning
Posted by Vladimir Ivanov <le...@gmail.com>.
Hi Jack!
Your thoughts regarding Redis integration seem very interesting.
Unfortunately I haven't had time to look closer into it. As I understood
from your comment - Lift's Record API doesn't fit well with Redis? Are you
going to use indrajitr's scala library for Redis?
I'm looking forward to see the results!
Vladimir
2011/9/6 Jack Park <ja...@topicquests.org>
> At the moment, I'm not sure about creating a Jira for it, but I am working
> on it. I started with https://github.com/indrajitr/**scala-redis<https://github.com/indrajitr/scala-redis>
> and, thanks to conversations with Indrajit, have learned that I can craft
> what I call RedisModel (an object) that holds a live instance of RedisClient
> and presents a useful API for doing timelines and nodes. I'm working on that
> now. RedisClient must be configured in Boot.scala
>
> When I get something that works, I'll toss it up to github and ask others
> to polish the work of this scala beginner.
>
> My present thinking is that user modeling is still handled in an RDBMS
> (though, I suppose, even there it's possible to run into scaling problems)
>
> Jack
>
>
> On 9/2/2011 10:25 AM, Ethan Jewett wrote:
>
>> That's a good point. Nothing with that level of scale is currently in
>> the realm of possibility for our use-cases, but as machine-generated
>> data becomes more prevalent it is going to become more of a problem.
>>
>> Want to create a Jira for it and assign it to the backlog? If you have
>> some ideas about how this should be done or want to work on a
>> prototype, go for it :-)
>>
>> Ethan
>>
>> On Fri, Sep 2, 2011 at 6:07 PM, Jack Park<ja...@topicquests.org>
>> wrote:
>>
>>> The interesting question for me is: how many records can you store in an
>>> RDBMS before you have to think about scale up issues? I wrote a trivial
>>> microblog in Java using Redis; I think there is a candidate fit.
>>>
>>> Cheers
>>> Jack
>>>
>>> On 9/1/2011 11:53 PM, Ethan Jewett wrote:
>>>
>>>>
>>>> It's certainly an interesting idea, and Lift does have some built-in
>>>> capabilities here in the form of the Record module. It would be a
>>>> pretty significant migration.
>>>>
>>>> An interesting question to explore: Would this give us a performance
>>>> boost in some scenarios?
>>>>
>>>> Cheers,
>>>> Ethan
>>>>
>>>> On Thu, Sep 1, 2011 at 10:54 PM, Jack Park<ja...@topicquests.org>
>>>> wrote:
>>>>
>>>>>
>>>>> Somewhat beyond 1.4, I'd like to ask about persistence other than
>>>>> RDBMS.
>>>>> For
>>>>> instance, in microblogging, there is some evidence that Redis can
>>>>> provide
>>>>> a
>>>>> scalable datastore.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> Cheers
>>>>> Jack
>>>>>
>>>>> On 8/29/2011 11:27 PM, Richard Hirsch wrote:
>>>>>
>>>>>>
>>>>>> I've been thinking about the next release and wanted to start
>>>>>> collecting ideas for features for this release.
>>>>>>
>>>>>> There are some tasks in Jira [1] but that list isn't complete:
>>>>>>
>>>>>> Here are some other ideas:
>>>>>>
>>>>>> * Integration with Akka / Apache Camel
>>>>>> * Simplification of URLs
>>>>>> * Change Web UI to deal with new icon
>>>>>>
>>>>>> Any one else have other ideas / suggestions?
>>>>>>
>>>>>> D.
>>>>>>
>>>>>> [1]
>>>>>>
>>>>>> https://issues.apache.org/**jira/secure/IssueNavigator.**
>>>>>> jspa?reset=true&jqlQuery=**project+%3D+ESME+AND+**
>>>>>> fixVersion+%3D+%221.4%22+AND+**status+%3D+Open+ORDER+BY+**
>>>>>> priority+DESC&mode=hide<https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ESME+AND+fixVersion+%3D+%221.4%22+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide>
>>>>>>
>>>>>
>>>>>
>>>
--
Best Regards,
Vladimir Ivanov
Re: 1.4 planning
Posted by Jack Park <ja...@topicquests.org>.
At the moment, I'm not sure about creating a Jira for it, but I am
working on it. I started with https://github.com/indrajitr/scala-redis
and, thanks to conversations with Indrajit, have learned that I can
craft what I call RedisModel (an object) that holds a live instance of
RedisClient and presents a useful API for doing timelines and nodes.
I'm working on that now. RedisClient must be configured in Boot.scala
When I get something that works, I'll toss it up to github and ask
others to polish the work of this scala beginner.
My present thinking is that user modeling is still handled in an RDBMS
(though, I suppose, even there it's possible to run into scaling problems)
Jack
On 9/2/2011 10:25 AM, Ethan Jewett wrote:
> That's a good point. Nothing with that level of scale is currently in
> the realm of possibility for our use-cases, but as machine-generated
> data becomes more prevalent it is going to become more of a problem.
>
> Want to create a Jira for it and assign it to the backlog? If you have
> some ideas about how this should be done or want to work on a
> prototype, go for it :-)
>
> Ethan
>
> On Fri, Sep 2, 2011 at 6:07 PM, Jack Park<ja...@topicquests.org> wrote:
>> The interesting question for me is: how many records can you store in an
>> RDBMS before you have to think about scale up issues? I wrote a trivial
>> microblog in Java using Redis; I think there is a candidate fit.
>>
>> Cheers
>> Jack
>>
>> On 9/1/2011 11:53 PM, Ethan Jewett wrote:
>>>
>>> It's certainly an interesting idea, and Lift does have some built-in
>>> capabilities here in the form of the Record module. It would be a
>>> pretty significant migration.
>>>
>>> An interesting question to explore: Would this give us a performance
>>> boost in some scenarios?
>>>
>>> Cheers,
>>> Ethan
>>>
>>> On Thu, Sep 1, 2011 at 10:54 PM, Jack Park<ja...@topicquests.org>
>>> wrote:
>>>>
>>>> Somewhat beyond 1.4, I'd like to ask about persistence other than RDBMS.
>>>> For
>>>> instance, in microblogging, there is some evidence that Redis can provide
>>>> a
>>>> scalable datastore.
>>>>
>>>> Thoughts?
>>>>
>>>> Cheers
>>>> Jack
>>>>
>>>> On 8/29/2011 11:27 PM, Richard Hirsch wrote:
>>>>>
>>>>> I've been thinking about the next release and wanted to start
>>>>> collecting ideas for features for this release.
>>>>>
>>>>> There are some tasks in Jira [1] but that list isn't complete:
>>>>>
>>>>> Here are some other ideas:
>>>>>
>>>>> * Integration with Akka / Apache Camel
>>>>> * Simplification of URLs
>>>>> * Change Web UI to deal with new icon
>>>>>
>>>>> Any one else have other ideas / suggestions?
>>>>>
>>>>> D.
>>>>>
>>>>> [1]
>>>>>
>>>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ESME+AND+fixVersion+%3D+%221.4%22+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
>>>>
>>
Re: 1.4 planning
Posted by Ethan Jewett <es...@gmail.com>.
That's a good point. Nothing with that level of scale is currently in
the realm of possibility for our use-cases, but as machine-generated
data becomes more prevalent it is going to become more of a problem.
Want to create a Jira for it and assign it to the backlog? If you have
some ideas about how this should be done or want to work on a
prototype, go for it :-)
Ethan
On Fri, Sep 2, 2011 at 6:07 PM, Jack Park <ja...@topicquests.org> wrote:
> The interesting question for me is: how many records can you store in an
> RDBMS before you have to think about scale up issues? I wrote a trivial
> microblog in Java using Redis; I think there is a candidate fit.
>
> Cheers
> Jack
>
> On 9/1/2011 11:53 PM, Ethan Jewett wrote:
>>
>> It's certainly an interesting idea, and Lift does have some built-in
>> capabilities here in the form of the Record module. It would be a
>> pretty significant migration.
>>
>> An interesting question to explore: Would this give us a performance
>> boost in some scenarios?
>>
>> Cheers,
>> Ethan
>>
>> On Thu, Sep 1, 2011 at 10:54 PM, Jack Park<ja...@topicquests.org>
>> wrote:
>>>
>>> Somewhat beyond 1.4, I'd like to ask about persistence other than RDBMS.
>>> For
>>> instance, in microblogging, there is some evidence that Redis can provide
>>> a
>>> scalable datastore.
>>>
>>> Thoughts?
>>>
>>> Cheers
>>> Jack
>>>
>>> On 8/29/2011 11:27 PM, Richard Hirsch wrote:
>>>>
>>>> I've been thinking about the next release and wanted to start
>>>> collecting ideas for features for this release.
>>>>
>>>> There are some tasks in Jira [1] but that list isn't complete:
>>>>
>>>> Here are some other ideas:
>>>>
>>>> * Integration with Akka / Apache Camel
>>>> * Simplification of URLs
>>>> * Change Web UI to deal with new icon
>>>>
>>>> Any one else have other ideas / suggestions?
>>>>
>>>> D.
>>>>
>>>> [1]
>>>>
>>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ESME+AND+fixVersion+%3D+%221.4%22+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
>>>
>
Re: 1.4 planning
Posted by Jack Park <ja...@topicquests.org>.
The interesting question for me is: how many records can you store in an
RDBMS before you have to think about scale up issues? I wrote a trivial
microblog in Java using Redis; I think there is a candidate fit.
Cheers
Jack
On 9/1/2011 11:53 PM, Ethan Jewett wrote:
> It's certainly an interesting idea, and Lift does have some built-in
> capabilities here in the form of the Record module. It would be a
> pretty significant migration.
>
> An interesting question to explore: Would this give us a performance
> boost in some scenarios?
>
> Cheers,
> Ethan
>
> On Thu, Sep 1, 2011 at 10:54 PM, Jack Park<ja...@topicquests.org> wrote:
>> Somewhat beyond 1.4, I'd like to ask about persistence other than RDBMS. For
>> instance, in microblogging, there is some evidence that Redis can provide a
>> scalable datastore.
>>
>> Thoughts?
>>
>> Cheers
>> Jack
>>
>> On 8/29/2011 11:27 PM, Richard Hirsch wrote:
>>>
>>> I've been thinking about the next release and wanted to start
>>> collecting ideas for features for this release.
>>>
>>> There are some tasks in Jira [1] but that list isn't complete:
>>>
>>> Here are some other ideas:
>>>
>>> * Integration with Akka / Apache Camel
>>> * Simplification of URLs
>>> * Change Web UI to deal with new icon
>>>
>>> Any one else have other ideas / suggestions?
>>>
>>> D.
>>>
>>> [1]
>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ESME+AND+fixVersion+%3D+%221.4%22+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
>>
Re: 1.4 planning
Posted by Ethan Jewett <es...@gmail.com>.
It's certainly an interesting idea, and Lift does have some built-in
capabilities here in the form of the Record module. It would be a
pretty significant migration.
An interesting question to explore: Would this give us a performance
boost in some scenarios?
Cheers,
Ethan
On Thu, Sep 1, 2011 at 10:54 PM, Jack Park <ja...@topicquests.org> wrote:
> Somewhat beyond 1.4, I'd like to ask about persistence other than RDBMS. For
> instance, in microblogging, there is some evidence that Redis can provide a
> scalable datastore.
>
> Thoughts?
>
> Cheers
> Jack
>
> On 8/29/2011 11:27 PM, Richard Hirsch wrote:
>>
>> I've been thinking about the next release and wanted to start
>> collecting ideas for features for this release.
>>
>> There are some tasks in Jira [1] but that list isn't complete:
>>
>> Here are some other ideas:
>>
>> * Integration with Akka / Apache Camel
>> * Simplification of URLs
>> * Change Web UI to deal with new icon
>>
>> Any one else have other ideas / suggestions?
>>
>> D.
>>
>> [1]
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ESME+AND+fixVersion+%3D+%221.4%22+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
>