search

EndPointCorp / end-point-blog

End Point Dev blog
https://www.endpointdev.com/blog/
17 stars 65 forks source link

Comments for RailsConf 2010: Spree and The Ecommerce Smackdown, Or Not #316

Open phinjensen opened 6 years ago

phinjensen commented 6 years ago

Comments for https://www.endpointdev.com/blog/2010/06/railsconf-2010-ecommerce-smackdown/ By Steph Skardal

To enter a comment:

  1. Log in to GitHub
  2. Leave a comment on this issue.
phinjensen commented 6 years ago 
original author: Ethan Rowe
date: 2010-06-15T00:27:02-04:00

I've got mixed feelings about ResourceController, myself; it has some good aspects to it and is not without its advantages. On the other hand, it feels like plain old nested resources would be perfectly fine and less restrictive in how one works with them.

But finding an alternative to SearchLogic would be truly fantastic. SearchLogic is pretty invasive. Making search easy is of course of vital importance to a project like Spree, but it seems to me that the right way forward would be to embrace the flexible, modular philosophy that has been used so effectively elsewhere in the platform; make searching a modular deal, where I can hook in my search engine by implementing a common interface. Don't force people to use a SQL-heavy, not-terribly-efficient, one-size-fits-all-except-large-or-fast solution. Sure, give a simple ActiveRecord-based one out of the box. But if I want to plug in to Sphinx, or Solr, or Lucandra, give me an interface to work with.

Thanks again for the conference coverage; it's great for those of us who couldn't make it.

phinjensen commented 6 years ago 
original author: Steph Powell
date: 2010-06-15T12:24:14-04:00

I think ResourceController is OK for the backend, but as soon as you get into complex role management requirements, you might consider building a role management friendly Spree backend base with the standard CRUD operations and before/after filter functionality. ResourceController doesn't really make sense for the frontend, as most of the frontend actions are limited. The one argument for keeping ResourceController is that the Spree core team would have to build a hook mechanism to allow before / after hook actions from the extensions as ResourceController allows.

Also, it looks like there are extensions written for the use of Solr and Sphinx in Spree, but these aren't advertised on the Spree extension directory (I found out through the spree-user google group).