On Sep 10, 9:06 am, Sam Smoot <[EMAIL PROTECTED]> wrote:
> On Aug 30, 6:57 pm, oldmoe <[EMAIL PROTECTED]> wrote:
>
> > I am still wondering why DO needs to rewrite every
> > driver from scratch?
> > If they see shortcomings in the current ones, why don't they just
> > contribute their fixes
> > so every one benefits?
>
> We don't rewrite the drivers. We've written a Ruby/C wrapper on top of
> the drivers. It's really a trivial effort for a C professional.
I believe his question was more on the lines of why doing your own
fork instead of contributing the .set_types methods to the "standard
drivers."
I do like the DO--it looks nice :)
re: fibers. The only reason they are nice is that they are cheaper
than threads. Somewhat of a hack to get cheap concurrency but hey, do
what you can.
If you have non-blocking drivers [ex: postgres' async_exec] then the
fiber can yield. Similar to saying "if you have non-blocking drivers
then you can switch threads waiting for a query to return."
Cheers!
-=R
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"DataMapper" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/datamapper?hl=en
-~----------~----~----~----~------~----~------~--~---
