I’ve been researching the best way to integrate ruby into the Shindig
opensocial container, so you can run your own opensocial container and
all your integration using ruby. Jruby is one option but I’m not sure
it’s the best. There are a few different ways I can tackle this.
provides a number of services, and it’s only the parts that retrieve
via rest and rpc that you need to implement on your own. There are
basically two ways of doing it. You can use the stubs in shindig and
java or php to do direct sql queries for your data, or you can
the entire rpc/rest interface yourself. I’ll probably open source
and I want the end user to be able to integrate with their system using
ruby,not java or php.
So anyways I was looking to see if jruby would be a good option.
I have a java stub, so I would need to use jruby inside java. I’ve read
wiki on how to do this using the java scripting stuff, it doesn’t seem
difficult. Assuming the new activerecord in rails 2.2 is really
I could use that. But I’m not sure about how stable the jruby inside
stuff is, how well it performs, and if I can rely on activercord in this
type of setup.
The other thing I have to consider though is that if I open source it,
implementation would people actually want to use. If I implement the
rcp/rest interfaces entirely in ruby, you would still need to run
provide metadata services, but it wouldn’t be something you would have
worry about scaling or knowing much about. You would only need to hit
when developers add/delete/update their opensocial applications. If I
shindig the way it was designed to work and just implement it’s stubs,
shindig would be taking all the traffic.
Anyways, for this group my main question is about the jruby integration.
the java scripting stuff the best approach? Is activerecord the only
for database stuff or is there a lower level jdbc interface I could use
still do it all in ruby?