Cool idea. In this case, I'm partially building my app and partially learning how to intelligently (well, down the road) build such a system myself. So while I'm using some plugins for some of the drudgery, like tagging, which I've done before, I'm explicitly trying to roll my own "recent activity" type services. So I'm thinking about how to do that without being monolithic.
But Lovd looks interesting, so I'll keep an eye on that. Thanks! On Dec 4, 4:35 pm, albemuth <[EMAIL PROTECTED]> wrote: > I'd say that's complicating yourself, I would check this > outhttp://lovdbyless.com/ > > On Dec 4, 9:02 am, justindz <[EMAIL PROTECTED]> wrote: > > > I'm getting to the point where my poetry app is taking on two roles: > > poetry app itself and "feed engine" (recent activity of contacts, > > recent comments on your stuff, etc.). It seems that the feed engine > > should probably be a separate, optimized web service for posting > > things asynchronously--latency can be traded for performance more > > easily than the main app. > > > Forgetting for a moment that this is probably the perfect job for > > Sinatra, what might be the best way to do this with Heroku? Create > > two apps and have them call each other? Has anyone done this and have > > pointers or pitfalls? Does this complicate anything for Heroku's > > eventual business model or violate any rules (using two apps to make > > one, in essence)? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
