# Embedding ruby in aolserver (Was: Re: segfault when calling

**URL:** <https://www.ruby-forum.com/t/embedding-ruby-in-aolserver-was-re-segfault-when-calling/61470>\
**Category:** Ruby\
**Created:** [May 24, 2006, 9:27am UTC](https://www.ruby-forum.com/t/embedding-ruby-in-aolserver-was-re-segfault-when-calling/61470 "2006-05-24T09:27:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tbobker](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/73ab20/32.png) [@tbobker](https://www.ruby-forum.com/u/tbobker)\
**Post date:** [May 24, 2006, 9:27am UTC](https://www.ruby-forum.com/t/embedding-ruby-in-aolserver-was-re-segfault-when-calling/61470/1 "2006-05-24T09:27:46Z")

</div>

Just because aolserver is multithreaded doesn’t mean that you need to  
access the ruby interpreter from each thread. Just make sure that only  
one thread accesses the interpreter at a time or create a single  
thread that access is funneled through.  
-tim

---

<div class="post-metadata">

**Author:** ![tbobker](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/73ab20/32.png) [@tbobker](https://www.ruby-forum.com/u/tbobker)\
**Post date:** [May 24, 2006, 8:23pm UTC](https://www.ruby-forum.com/t/embedding-ruby-in-aolserver-was-re-segfault-when-calling/61470/2 "2006-05-24T20:23:05Z")

</div>

On May 24, 2006, at 3:24 AM, Tim B. wrote:

> >

I think part of the reason he wanted to do this (after all there’s  
already mod\_ruby, mongrel and fastcgi) is precisely because of  
aolserver’s thread-heavy architecture. Using only one interpreter  
kinda kills the point.