Socket Connections / URLFetchService

[Sandro Röder]

Hi,

is it possible to create socket like connections vie URLFetch service.

I need a similar implantation to the following code:

Socket s=new Socket();

s.connect(new InetSocketAddress("somehost.com",
3000));
i=s.getInputStream();
o=s.getOutputStream();

Does anybody know how to implement this via the URLFetchService

Thanks,
Sandro

[Simon Knott]

You can't I'm afraid, HTTP is the only protocol which is allowed from a GAE-hosted application.

Cheers,

Simon

[Sandro Röder]

Thanks a lot.

Thats stupid, then I can forget appengine.

[Brandon Wirtz]

No. It is Purpose built. Rather than being all things to all people GAE has
one purpose, FAST web Services.

It's not a game server, a mail relay, a distributed computing farm. As a
result it is scalable predictable and supportable.

Thanks a lot.

--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengi...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.

[Andrin von Rechenberg]

well, it's actually a quite cool distributed

computing farm with the task queue support -

it's just a rather expensive one.

[André Pankraz]

But after all I have seen now I think, wouldn't a mixed system PAAS and IAAS be better?

So keep this whole Services, but add free configurable virtual servers like Amazon.

Then you have H/R and BlobStore for Data, Queues, Crons, Frontend Channels, Email etc.
Replace Backend servers with AWS like servers, with the option to use them as alternative more flexible Frontend with configurable Load balancer. I understand why something like Backend servers can help to offload long running stuff to keep the Frontends for low latency stuff - but the restrictions are too tight.