Hey!  

I don’t like such additional connector modules. They have their own bugs and 
generating system-wide errors, mostly. Especially when the module has an own 
style and/or database tables far from oxid. I had scenarios within a customer 
tried to remove a connectors modul and gets a lot of trouble with the system. 
But if you want to get rich with support, this could be a model ;)

What about a wrapper script inside every module or inside the vendor structure? 
With that you can also check the versions and be agile.  






Mit freundlichen Grüßen


Marcel Müller
Webentwicklung / Projektmanagement
eMail: [email protected] (mailto:[email protected])



aikme GmbH
Rheinstraße 43-45
55116 Mainz / Deutschland
Telefon: 06131 92 06 503
Telefax: 06131 92 08 334
www.aikme.de (http://www.aikme.de/)

aikme GmbH  
Geschäftsführer: Sascha Coldewey  
Sitz in Mainz, Registergericht: Mainz  
Registernummer: HRB 44835  
Umsatzsteuer ID: DE282561622  




Am Dienstag, 21. Januar 2014 um 08:31 schrieb Roman Allenstein:

> Hi folks,
>  
> me and my team are developing a concept for us, how to develop modules  
> for oxid. We are now at the point where we have to decide to develope a  
> connector-module for all our coming modules or not.
>  
> We know that some agecies use their own connector to integrate their  
> modules in oxid. And i am pretty unsure if this is the way to go because  
> oxid provides a standardized way to integrate modules.
>  
> Whats your pros and cons for using an own connector?
>  
> Greets
> Roman
> --  
> Dipl.Winf. (FH) Roman Allenstein
> Sales Manager E-Commerce
> Spark 5 GmbH
> Lutherstraße 7
> 27570 Bremerhaven
>  
> Fon: +49-471-4836-3547
> Fax: +49-6151-8508-111
>  
> Mail: [email protected] (mailto:[email protected])
> Web: http://www.spark5.de
> --
>  
> Geschäftsführer:
> Dipl. Designer Till Middelhauve
> Dipl. Informatiker Witold Wegner
> Amtsgericht Darmstadt, HRB 7809
>  
> Diese E-Mail könnte vertrauliche und/oder rechtlich geschützte  
> Informationen enthalten. Wenn Sie nicht der richtige Adressat sind oder  
> diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den  
> Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie  
> die unbefugte Weitergabe dieser Mail sind nicht gestattet.
>  
> This e-mail may contain confidential and/or privileged information. If  
> you are not the intended recipient (or have received this e-mail in  
> error) please notify the sender immediately and destroy this e-mail. Any  
> unauthorised copying, disclosure or distribution of the material in this  
> e-mail is strictly forbidden.
> _______________________________________________
> dev-general mailing list
> [email protected] (mailto:[email protected])
> http://dir.gmane.org/gmane.comp.php.oxid.general
>  
>  


_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

Reply via email to