you'd have to wonder if there's a push out to Gnip somewhere ... or if
protocol buffers are involved ..
Thanks-
- Andy Badera
- and...@badera.us
- (518) 641-1280
- Tech Valley Code Camp 2009.1: http://www.techvalleycodecamp.com/
- Google me: http://www.google.com/search?q=andrew+badera
On Wed
Hmm. Good thinking Andrew. I've done a bit more digging along those
lines..I don't think Jaiku has publically said if and what messaging
protocols they might use, but there seems to be some speculation that
it uses XMPP.
That might also neatly align with their comment that they are in some
cases
I've done a good bit of googling about what exactly it is I'm trying
to achieve, the correct terminology etc. and turns out I'm really
looking for an efficient way to do pub/sub, publication/subscription,
on appengine.
Which led me to this eyebrow-raising little app from Brett Slakin and
Brad Fit
great find peterk! cant help but notice the very interesting
async_apiproxy.py code in that project either...async db and url calls
would be awesome
cheers
brian
On Mar 11, 3:22 pm, peterk wrote:
> I've done a good bit of googling about what exactly it is I'm trying
> to achieve, the correct te
The app is actually live here:
http://pubsubhubbub.appspot.com/
http://pubsubhubbub-subscriber.appspot.com/
(pubsubhubbub-publisher isn't there, but it's trivial to upload your
own.)
This suggests it's working on appengine as it is now. Been looking
through the source, and I'm not entirely clea
I implemented a very basic microblog app:
http://microbloog.appspot.com/
Regards!
On Mar 11, 10:21 am, peterk wrote:
> I just read on your blog (from January) the intention to release the
> appengine port of Jaiku as open source when the port is finished..but
> I was wondering if I could be so
right, i can't really tell either. it looks like the churn of incoming
requests is powering the "background" workers, the real change is the
async proxy (AsyncAPIProxy.start_call) to fire the workers off without
affecting the incoming request (at least I think thats what is
happening...)
it would
The urls at /work/pull_feeds and /work/push_events seem to manually
trigger the 'background' work of pulling feeds and pushing events..but
I've still yet to actually get it working :p In the demo vid it seems
to work beautifully, with instantaneous results.
There is a tiny group for pubsubhubub,
Heyo,
Good finds, peterk!
pubsubhubbub uses some of the same techniques that Jaiku uses for
doing one-to-many fan-out of status message updates. The migration is
underway as we speak
(http://www.jaiku.com/blog/2009/03/11/upcoming-service-break/). I
believe the code should be available very soon.
Just Curious,
For other pub/sub-style systems where you want to write to the
Datastore, the trick is to use list properties to track the
subscribers you've published to. So for instance, instead of writing a
single entity per subscriber, you write one entity with 1000-2000
subscriber IDs in a list
I was just toying around with this idea yesterday Brett.. :D I did
some profiling, and it would reduce the write cost per subscriber to
about 24ms-40ms (depending on the number of subscribers you have..more
= lower cost per avg), from 100-150ms. These are rough numbers with
entities I was using, I
@peterk - if you don't need to query by the subscriber, you could
alternatively pack the list of subscribers for a feed into a
TextProperty so it is not indexed. I use TextProperty a lot to store
large lists of geometry data and they work out pretty well
@brett - async! looking forward to it in f
Unfortunately I do need to query them based on subscriber_id..so I
can't pack them into a non-indexed property.
Retrieving updates particular user has subscribed to is blazingly fast
though...that's the gain in the end, I can query and fetch 1000
updates for a user sorted by date in 20-30ms-cpu.
Just a head's up - Jaiku has gone open source :)
http://code.google.com/p/jaikuengine/
At a very brief first glance, I see references to xmpp stuff and
more..going to try and map out the code and see what goodies might be
there, could be stuff of interest beyond pub/sub too.
On Mar 13, 1:28 pm,
By the way, we do something very similar at Sponty (http://
www.thesponty.com/boston). We're adding a new feature whereby when one
of your friends posts an event, we notify his or her friends via
email, sms or twitter. It would take too long to process those
communique right away. So we just write
I am really stoked by the fact that it is now open. I love seeing how other
people develop software.
Paul.
2009/3/14 peterk
>
> Just a head's up - Jaiku has gone open source :)
>
> http://code.google.com/p/jaikuengine/
>
> At a very brief first glance, I see references to xmpp stuff and
> more
I know the topic is more about microblogging services than xmpp, but
by chance, have somebody achieved to install some comet/ajax push
applications? The technique might be used to speed up message display
for popular conversations as it is used for the chat function in
google mail.
--~--~-
Wouldn't a Comet mechanism be fairly expensive, implemented on GAE?
On Sun, Mar 15, 2009 at 7:59 AM, thuan wrote:
>
> I know the topic is more about microblogging services than xmpp, but
> by chance, have somebody achieved to install some comet/ajax push
> applications? The technique might be u
2009/3/15 thuan :
>
> I know the topic is more about microblogging services than xmpp, but
> by chance, have somebody achieved to install some comet/ajax push
> applications? The technique might be used to speed up message display
> for popular conversations as it is used for the chat function in
The XMPP support mentioned on the roadmap does not include BOSH.
-- Dan
On Sun, Mar 15, 2009 at 6:14 PM, David Wilson wrote:
>
> 2009/3/15 thuan :
> >
> > I know the topic is more about microblogging services than xmpp, but
> > by chance, have somebody achieved to install some comet/ajax push
>
Thanks for that Dan.
I just noticed that quite surprisingly, time.sleep() works.
David.
2009/3/16 Dan Sanderson :
> The XMPP support mentioned on the roadmap does not include BOSH.
> -- Dan
>
> On Sun, Mar 15, 2009 at 6:14 PM, David Wilson wrote:
>>
>> 2009/3/15 thuan :
>> >
>> > I know the t
> I just noticed that quite surprisingly, time.sleep() works.
There is a 10 second execution limit for all requests. This includes
requesting and submitting data to external services. Long polling
would not be that easy to sustain. I'm still looking for a way to
circumvent this limitation, if any
use a URL monitoring service to ping your URLs every n minutes ...
On Mon, Mar 16, 2009 at 6:40 AM, thuan wrote:
>
>> I just noticed that quite surprisingly, time.sleep() works.
>
> There is a 10 second execution limit for all requests. This includes
> requesting and submitting data to extern
23 matches
Mail list logo