You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Ian Wilson <ia...@gmail.com> on 2010/04/16 23:32:57 UTC
Questions/Python
Hi,
I'm just researching around about social networking. I'm thinking about
starting my own social site although I'm not sure if I should just be making
apps for existing social sites. Shindig looks like a really fast way to get
started but I have a few questions.
Does shindig have an IRC channel set up? So I can ask even more questions.
A users list is mentioned in the mailing list section of the site but the
archives do not exist. Does this list really exist? This email might be
more appropriate for that list, sorry if that is the case.
Has anyone shown interest in porting shindig to python? I saw this
http://code.google.com/p/gae-opensocial/ but I haven't heard that many good
things about GAE, I think its still too unrefined. I know this is nearly an
impossible software engineering feat but how long do you think it would take
a developer to port over the most minimal working portion of shindig to
python? Most of my experience lies in python I have not used java or php in
over 5 years.
Would running shindig as a backend process that a python frontend proxies to
be feasible from a performance perspective and/or make sense?
Thanks for your time,
-Ian
Re: Questions/Python
Posted by Santiago Gala <sa...@gmail.com>.
On Tue, Apr 20, 2010 at 8:11 PM, Ian Wilson <ia...@gmail.com> wrote:
> Thanks for the responses. I'm glad people are able to use shindig
> without porting it.
>
> Okay it sounds like I should just stick with php or java and (bite the
> bullet) write the db layer as you both suggested since I'm using a
> rdbms. I think I'm going to use java because I already need some
> sort of setup with lucene. Although my java skills are atrocious.
>
If you need to interface with java APIs and you are python house you
might consider jython. From my experience it is very good to have
python code interfacing with java. It has been some time since I last
used it, and the main problem used to be that the pòrt was lagging a
lot behind the native one...
Regards
Santiago
> I'm still reading up on opensocial, there are a ton of specs! I'm not
> entirely sure how the parts go together yet. I built the java version
> of shindig but its still all magic to me. I think I will have tons of
> questions but I can't quantify them now. Thanks again for the help.
> I'm sure I'll be back with more questions later.
>
> -Ian
>
>
> On Sat, Apr 17, 2010 at 12:08 PM, Tim Wintle <ti...@teamrubber.com> wrote:
>> I am running PHP Shindig supporting a main application built in
>> Python...
>>
>> On Fri, 2010-04-16 at 14:32 -0700, Ian Wilson wrote:
>>> Has anyone shown interest in porting shindig to python? I saw this
>>> http://code.google.com/p/gae-opensocial/ but I haven't heard that many good
>>> things about GAE, I think its still too unrefined. I know this is nearly an
>>> impossible software engineering feat but how long do you think it would take
>>> a developer to port over the most minimal working portion of shindig to
>>> python?
>>
>> I believe there is at least one other port somewhere - I've certainly
>> seen a good port of most of the code to Python at some point.
>>
>> Shindig is maintained with the latest features far more quickly than you
>> could expect other ports to be though (IMO). That's the reason I haven't
>> moved to a Python port (at least yet).
>>
>> I chose PHP because we do have some in-house PHP devs I can go to if
>> required (but not Java), and we don't have any JVMs on our production
>> boxes - but otherwise it would have made little difference to me so far.
>>
>> Personally I'm mainly using the gadgetserver part of shindig - which
>> requires little direct integration between the two pieces of software
>> (shindig and the main app). Deployment is basically just patching
>> shindig with some javascript features, configuration changes and a few
>> minor patches.
>>
>> As I'm only using the gadgetserver, the gadgets/metadata call gives me
>> most of the shindig-container communication I need, and the /gadgets/ifr
>> call gives most of the container-shindig communication.
>>
>> Regarding the main social apis, if your data from python is stored into
>> a relational database then it's probably easiest to bite the bullet and
>> extend the appropriate shindig apis within php/java - A large part of my
>> data is stored in a zope object database, so that hasn't been an option
>> for me, and as far as I know the other options are basically:
>>
>> * Not implement the actual opensocial parts (not recommended unless
>> it's really not required)
>>
>> * Implement the social interfaces in shindig so that they make requests
>> to your main app (via JSON-RPC or similar)
>>
>> * Implement the Rest apis in python and modify the apache config to
>> send specific requests to different services.
>>
>> Hope that helps,
>>
>> Tim Wintle
>>
>>
>
Re: Questions/Python
Posted by Ian Wilson <ia...@gmail.com>.
Thanks for the responses. I'm glad people are able to use shindig
without porting it.
Okay it sounds like I should just stick with php or java and (bite the
bullet) write the db layer as you both suggested since I'm using a
rdbms. I think I'm going to use java because I already need some
sort of setup with lucene. Although my java skills are atrocious.
I'm still reading up on opensocial, there are a ton of specs! I'm not
entirely sure how the parts go together yet. I built the java version
of shindig but its still all magic to me. I think I will have tons of
questions but I can't quantify them now. Thanks again for the help.
I'm sure I'll be back with more questions later.
-Ian
On Sat, Apr 17, 2010 at 12:08 PM, Tim Wintle <ti...@teamrubber.com> wrote:
> I am running PHP Shindig supporting a main application built in
> Python...
>
> On Fri, 2010-04-16 at 14:32 -0700, Ian Wilson wrote:
>> Has anyone shown interest in porting shindig to python? I saw this
>> http://code.google.com/p/gae-opensocial/ but I haven't heard that many good
>> things about GAE, I think its still too unrefined. I know this is nearly an
>> impossible software engineering feat but how long do you think it would take
>> a developer to port over the most minimal working portion of shindig to
>> python?
>
> I believe there is at least one other port somewhere - I've certainly
> seen a good port of most of the code to Python at some point.
>
> Shindig is maintained with the latest features far more quickly than you
> could expect other ports to be though (IMO). That's the reason I haven't
> moved to a Python port (at least yet).
>
> I chose PHP because we do have some in-house PHP devs I can go to if
> required (but not Java), and we don't have any JVMs on our production
> boxes - but otherwise it would have made little difference to me so far.
>
> Personally I'm mainly using the gadgetserver part of shindig - which
> requires little direct integration between the two pieces of software
> (shindig and the main app). Deployment is basically just patching
> shindig with some javascript features, configuration changes and a few
> minor patches.
>
> As I'm only using the gadgetserver, the gadgets/metadata call gives me
> most of the shindig-container communication I need, and the /gadgets/ifr
> call gives most of the container-shindig communication.
>
> Regarding the main social apis, if your data from python is stored into
> a relational database then it's probably easiest to bite the bullet and
> extend the appropriate shindig apis within php/java - A large part of my
> data is stored in a zope object database, so that hasn't been an option
> for me, and as far as I know the other options are basically:
>
> * Not implement the actual opensocial parts (not recommended unless
> it's really not required)
>
> * Implement the social interfaces in shindig so that they make requests
> to your main app (via JSON-RPC or similar)
>
> * Implement the Rest apis in python and modify the apache config to
> send specific requests to different services.
>
> Hope that helps,
>
> Tim Wintle
>
>
Re: Questions/Python
Posted by Tim Wintle <ti...@teamrubber.com>.
I am running PHP Shindig supporting a main application built in
Python...
On Fri, 2010-04-16 at 14:32 -0700, Ian Wilson wrote:
> Has anyone shown interest in porting shindig to python? I saw this
> http://code.google.com/p/gae-opensocial/ but I haven't heard that many good
> things about GAE, I think its still too unrefined. I know this is nearly an
> impossible software engineering feat but how long do you think it would take
> a developer to port over the most minimal working portion of shindig to
> python?
I believe there is at least one other port somewhere - I've certainly
seen a good port of most of the code to Python at some point.
Shindig is maintained with the latest features far more quickly than you
could expect other ports to be though (IMO). That's the reason I haven't
moved to a Python port (at least yet).
I chose PHP because we do have some in-house PHP devs I can go to if
required (but not Java), and we don't have any JVMs on our production
boxes - but otherwise it would have made little difference to me so far.
Personally I'm mainly using the gadgetserver part of shindig - which
requires little direct integration between the two pieces of software
(shindig and the main app). Deployment is basically just patching
shindig with some javascript features, configuration changes and a few
minor patches.
As I'm only using the gadgetserver, the gadgets/metadata call gives me
most of the shindig-container communication I need, and the /gadgets/ifr
call gives most of the container-shindig communication.
Regarding the main social apis, if your data from python is stored into
a relational database then it's probably easiest to bite the bullet and
extend the appropriate shindig apis within php/java - A large part of my
data is stored in a zope object database, so that hasn't been an option
for me, and as far as I know the other options are basically:
* Not implement the actual opensocial parts (not recommended unless
it's really not required)
* Implement the social interfaces in shindig so that they make requests
to your main app (via JSON-RPC or similar)
* Implement the Rest apis in python and modify the apache config to
send specific requests to different services.
Hope that helps,
Tim Wintle
Re: Questions/Python
Posted by Evgeny Bogdanov <ev...@epfl.ch>.
On 16/4/10 23:32, Ian Wilson wrote:
> Hi,
>
> I'm just researching around about social networking. I'm thinking about
> starting my own social site although I'm not sure if I should just be making
> apps for existing social sites. Shindig looks like a really fast way to get
> started but I have a few questions.
>
> Does shindig have an IRC channel set up? So I can ask even more questions.
>
> A users list is mentioned in the mailing list section of the site but the
> archives do not exist. Does this list really exist? This email might be
> more appropriate for that list, sorry if that is the case.
>
> Has anyone shown interest in porting shindig to python? I saw this
> http://code.google.com/p/gae-opensocial/ but I haven't heard that many good
> things about GAE, I think its still too unrefined. I know this is nearly an
> impossible software engineering feat but how long do you think it would take
> a developer to port over the most minimal working portion of shindig to
> python? Most of my experience lies in python I have not used java or php in
> over 5 years.
>
> Would running shindig as a backend process that a python frontend proxies to
> be feasible from a performance perspective and/or make sense?
>
Hi,
I have rails server and php shindig on the same machine.
I use the same database for both. For shindig you have to implement
several database requests,
which doesn't require a lot of php skills. You can just take paruza
classes and change them appropriately
to your requirements.
I am completely satisfied!
Don't really see a need for ruby version of shindig :)
Best
Evgeny
> Thanks for your time,
>
> -Ian
> .
>
>