Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
CORS
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
emma lopez  
View profile  
 More options Oct 30 2012, 7:17 am
From: emma lopez <eraseuna...@gmail.com>
Date: Tue, 30 Oct 2012 04:17:07 -0700 (PDT)
Local: Tues, Oct 30 2012 7:17 am
Subject: CORS

Any plans to have CORS enabled in 37signals-api?

Last messages are from 2009 and all work was in dev side: by proposing to
have a proxy.

Has policy changed? Any plans in near future?

With some great js frameworks and mobile webapps in the market, wouldnt you
guys like to contribute to the standars and make life easier to developers?
I would love to hear about you!

Emma
Signed: a js dev who would like to create a webapp for campfire *without*
setting a proxy


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jeremy Kemper  
View profile  
 More options Oct 30 2012, 11:49 am
From: Jeremy Kemper <jer...@37signals.com>
Date: Tue, 30 Oct 2012 08:49:00 -0700
Subject: Re: [37signals API] CORS

On Tue, Oct 30, 2012 at 4:17 AM, emma lopez <eraseuna...@gmail.com> wrote:
> Any plans to have CORS enabled in 37signals-api?

> Last messages are from 2009 and all work was in dev side: by proposing to
> have a proxy.

> Has policy changed? Any plans in near future?

> With some great js frameworks and mobile webapps in the market, wouldnt you
> guys like to contribute to the standars and make life easier to developers?
> I would love to hear about you!

> Emma
> Signed: a js dev who would like to create a webapp for campfire *without*
> setting a proxy

Hi Emma,

We'd love to support CORS. It is a significant development effort,
however. We don't have concrete plans.

No policy against it, by any means!

--
Jeremy Kemper
37signals


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »