3 ms·

Thanks for the pointer. You should check out Microsoft Windows Azure AppFabric Service Bus (http://www.microsoft.com/windowsazure/AppFabric/Overview/default.asp

Thanks for the pointer. You should check out Microsoft Windows Azure AppFabric Service Bus (http://www.microsoft.com/windowsazure/AppFabric/Overview/default.aspx http://www.microsoft.com/windowsazure/AppFabric/Overview/def...). It's supported for .NET by MSFT; however, I think there are other implementations for other platforms. Technologically it is very similar. (I used to be a Program Manager on that team not long ago). I understand the technology quite well; however, (hope I don't sound rude) I'm not clear on what the value is to the customer (presumably developer) of pagekite.net. Please email me; my email address is on http://www.skierkowski.com/ http://www.skierkowski.com/ (I have CAPTCHA on there which is why I don't just give it to you here).

HerraBRE 16y ago
Just to answer here as well (I'll be in touch), the easiest pitch is to content creators who want to remove the "deploy stuff to some server in order to show progress to clients and coworkers" step from their work flow. Obviously, this is most applicable to people working on web designs or web app development. Another way to think of it, is that anyone who uses dynamic DNS today might find PageKite is a better fit for certain tasks. Dynamic DNS only works when a device is immobile and you have a visible, unfiltered IP. PageKite doesn't have those limitations, and is way easier to set up. There are many reasons to want to be able to run a simple server on a personal computing device, we've just been beaten out of the habit of even considering it by firewalls and NAT. So you are absolutely right that the value is often unclear to people at first - we have a definite up-hill struggle ahead in marketing this. I am optimistic though, because so far most techies who have given it a try found it so convenient all their objections melted away.

HerraBRE 16y ago

Just to answer here as well (I'll be in touch), the easiest pitch is to content creators who want to remove the "deploy stuff to some server in order to show progress to clients and coworkers" step from their work flow. Obviously, this is most applicable to people working on web designs or web app development. Another way to think of it, is that anyone who uses dynamic DNS today might find PageKite is a better fit for certain tasks. Dynamic DNS only works when a device is immobile and you have a visible, unfiltered IP. PageKite doesn't have those limitations, and is way easier to set up. There are many reasons to want to be able to run a simple server on a personal computing device, we've just been beaten out of the habit of even considering it by firewalls and NAT. So you are absolutely right that the value is often unclear to people at first - we have a definite up-hill struggle ahead in marketing this. I am optimistic though, because so far most techies who have given it a try found it so convenient all their objections melted away.