Re: The problem with OSS [long]

judgej <[email protected]>
Newsgroups gmane.comp.web.oscommerce.suggestions
Message-ID <f46774261f9337ff1e2e8d2586170012@osCommerce-Forums>
This message was sent from: Suggestions and Proposals
http://forums.oscommerce.com/viewtopic.php?p=190592#190592
----------------------------------------------------------------

[quote="stevepurkiss"]...Believe it or not, people /do/ want integrated CMS and Commerce - why should people have to spend many weeks integrating diverse systems? Integrated ones will always win, which is why *nukes are so popular.

...

Integrate, don't disintegrate.
[/quote]

I would add: interoperate, don't isolate.

I think the crux is in how the integration is done. If the cart is too closely bound to the CMS, then it would reduce the choice for the end users, as the OSC cart would only be usable within one CMS. As you have found - there is no perfect CMS for all people, so that would not be a good move.

If APIs were built between the cart and the CMS functionality, then it would be possible to replace the CMS part with any CMS going. That, I believe, would increase the choice and versatility of the cart, and the hence userbase. It all depends on whether the OSC project wants to see fragmented ports to other systems: oscnuke, xarosc, oscxoops; or OSC running within all those CMSs as an application in its own right, but sharing the CMSs' security structures, sessions and data.

I'm not asking anyone on the project to actually do this, but it would be nice to know exactly what the objection is to the whole concept of interoperability with other applications. The whole idea just seems to be dismissed out of hand.

From an end user persective: I have already chosen my CMS, now I am choosing the cart that will operate [i]within[/i] it.

-- Jason
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.