On Nov 10, 2007 1:37 AM, Orion Delwaterman <orion at mh2o.com>
wrote:> So what protocol is it being switched to?
For internal communication between workers, its just Marshal.load and
Marshal.dump with a uniq message header ( or footer ), that indicates
end of message. When worker or master reads a message thats complete,
it calls Marshal.load on it, and passes it around. I guess, that would
be even lighter than DRb, but may not be as much versatile. But with
this release of bdrb, I am more concerned about stability of stuff
than features.
>
>
> -----Original Message-----
> From: hemant [mailto:gethemant at gmail.com]
> Sent: Friday, November 09, 2007 3:07 PM
> To: Orion Delwaterman
> Cc: backgroundrb-devel at rubyforge.org
> Subject: Re: [Backgroundrb-devel] Why the switch to SMTP
>
> On Nov 9, 2007 9:35 PM, Orion Delwaterman <orion at mh2o.com> wrote:
> > Can anyone explain why BackgrounDRb is switching form DRb to SMTP
> > protocol? That seems like a lot of overhead to add to the messaging
> > back and forth?
>
> Its not being switched to SMTP protocol. I don''t know from where
that
> information comes from.
> But yes we are definitely getting rid of drb.
>
>
>
> Let them talk of their oriental summer climes of everlasting
> conservatories; give me the privilege of making my own summer with my
> own coals.
>
> http://gnufied.org
>
--
Let them talk of their oriental summer climes of everlasting
conservatories; give me the privilege of making my own summer with my
own coals.
http://gnufied.org