Deployment

10 views
Skip to first unread message

Brian O'Connor

unread,
Mar 28, 2011, 1:26:11 PM3/28/11
to hoo...@googlegroups.com
Hello everyone,

What are the best practices so far for deploying hookbox? I was going to deploy on hookbox.example.com, but we're afraid of it breaking the same domain policy of ajax.  Does hookbox get around that somehow?

Thanks in advance,
Brian



--
Brian O'Connor

Rob Weiss

unread,
Mar 28, 2011, 1:32:14 PM3/28/11
to hoo...@googlegroups.com
It should not be an issue, since the callback server (your app server) will get every message via a standard http post/get...

Have you played with the hosted hookbox?

Brian O'Connor

unread,
Mar 28, 2011, 1:40:22 PM3/28/11
to hoo...@googlegroups.com
I'm not worried about the callbacks, I'm worried about the streaming between the clients and hookbox.

If our application page is hosted at example.com, and hookbox is loading messages through hookbox.example.com, it won't have any problems with the cross domain policy enforced by browsers?
--
Brian O'Connor

Rob Weiss

unread,
Mar 28, 2011, 1:49:39 PM3/28/11
to hoo...@googlegroups.com
Not if I recall, I think the client side JS uses JSONP..... try it!!

Brian O'Connor

unread,
Mar 28, 2011, 1:54:15 PM3/28/11
to hoo...@googlegroups.com
Thanks Rob, I'll try it out tonight.  Is there a recommended server to use? Apache, nginx, something I haven't heard of yet? 

We'd obviously like to take advantage of websockets, but if that's not doable in production, we can wait.  Is it okay to just expose hookbox itself and not proxy it?
--
Brian O'Connor

Andy K

unread,
Mar 29, 2011, 4:29:51 AM3/29/11
to Hookbox User Group
Hello Brian,

As been explained by Rob, yes, it should not be an issue if your
hookbox runs on a different subdomain.
I've tried both running hookbox on different domain and specifying
only IP address, and on both it seems to work ok.

Rob Weiss

unread,
Mar 29, 2011, 6:14:34 AM3/29/11
to hoo...@googlegroups.com
hmmm.. depends on your authentication scheme. I am using a pretty tight security policy to control who/what can access my hb.

I will be adding SSL/TLS support to everything hb related real soon. Client side and server side. So you can expect that we will put that out for release within the next couple of weeks (hopefully!).

My back end for the hb and call back server is python.

WS are only available on the front end client in Chrome right now, but the client JS will control the connection (http long-poll vs. ws) so when they become more wide spread, it will figure it out itself.

There has been some chatter about nginx as a proxy, but I know nothing about that.

You can hit us up all day on the IRC @ #hookbox - if you need a quicker response.

Thanks,
Rob.
Reply all
Reply to author
Forward
0 new messages