Yeah,<br><br>because my small little pea brain is trying to wrap my head around Smalltalk and Seaside I'm trying to minimize the additional layers above and beyond that. I know that some would say that something like GLASS or Web Velocity would simplify the process. My feeling is that it's just more framework that I have to try and wrap my head around and I'm having enough problems right now just getting my head to work in the Smalltalk object paradigm. <br>
<br>My concerns with using just Smalltalk for the persistence layer is that eventually I want to integrate with something written in Java, or C or just provide a data feed through a desktop app. For me that suggests that a RDMS solution is more general purpose. My guess also as I move forward if I can ever find someone who is willing to pay me for Smalltalk work, that it would be easier to sell a solution with an RDMS data store. In addition it's always possible that I might need to integrate with some kind of legacy data available only in an RDMS. For all those reasons, RDMS seems like the "better" solution, even given the impedance mismatch between objects and RDBM systems.<br>
<br>I realize I could probably get the all Smalltalk solution to work as also, but for now I'm more comfortable with a RDBMS data store. <br><br>Tony<br><br><div class="gmail_quote">On Wed, Nov 4, 2009 at 10:05 AM, James Foster <span dir="ltr"><<a href="mailto:Smalltalk@jgfoster.net">Smalltalk@jgfoster.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Tony,<br>
<br>
I have a tutorial on how to setup up GLASS (GemStone, Linux, Apache, Seaside, & Smalltalk) on a 256 MB Slicehost ($20/month). See <a href="http://programminggems.wordpress.com/2008/09/05/setting-up-glass-on-slicehost/" target="_blank">http://programminggems.wordpress.com/2008/09/05/setting-up-glass-on-slicehost/</a>. As to the best database, why not use Smalltalk and avoid the O/R mapping problems?<br>
<font color="#888888">
<br>
James</font><div><div></div><div class="h5"><br>
<br>
On Nov 3, 2009, at 5:19 PM, Tony Giaccone wrote:<br>
<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">
<br>
I'm interested in putting together a small linux server that will support seside as a web application server.<br>
<br>
I'm curious about what characteristics are appropriate?<br>
<br>
Memory size?<br>
Disk Size?<br>
Linux distro?<br>
<br>
I'll probably be using glorp and mysql or postgres on the same box.<br>
<br>
Is there a consensus on which DB is a better choice?<br>
<br>
<br>
Tony<br></div></div><div class="im">
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></blockquote><div><div></div><div class="h5">
<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></div></blockquote></div><br>