Feedly API Authentication

[Dennis Effing]

Hi, I'm a student at a university in Germany and a few fellow students and I want to develop an RSS-Reader App for Android with feedly integration.

I am responsible for a Feedly API Client that we can use in the application and have read the most part of the feedly documentation at www.developer.feedly.com.
A few questions have come up and I hope that someone here is able to answer them for me since I'm a little overwhelmed right now.

1. As far as I understand it, you need a API key to make API calls. What is the difference between the sandbox environment and a developer token you can retrieve at https://feedly.com/v3/auth/dev?
2. How are you able to login via Facebook/Google? I have read the page about OAuth Authentification at http://developer.feedly.com/v3/auth and I understand the concept with client_id, client_secret and so on but I don't understand how Facebook/Google comes into play.
3. How do I use the redirect_uri? Let's say I want to obtain a code and send the response_type, redirect_uri, scope, state in a quick and dirty little java application, how do I retrieve the response?

Regards

[David Chatenay]

  Hi Dennis,

  Here are some answers:

1. Sandbox is a development and test environment, where you can build your app without a production client id and secret. Once your app is ready to ship, you can request a production client id and secret, and change the API URLs to use cloud.feedly.com. Then your application can be distributed on the Android App store for example: existing feedly users will be able to login with their account.

A Developer token is useful to make some quick prototyping, or some personal application for a single user. It will not enable you to build an application that can be used by other users.

2. This happens in the authentication window. Your app will have to open a webview and point it to https://sandbox.feedly.com/v3/auth/auth?client_id=... etc. This window will show the login selection (Google/Facebook/Twitter etc). It will look like the login experience when you go to https://sandbox.feedly.com and click on "login".

3. Once the user is logged in, the feedly server will send a redirect in the webview to the redirect_uri specified in the auth URL. Your app will need to "intercept" this redirect, extract the code from the URL, and call the token API to get a refresh_token and an access_token. From there you can dispose of the webview and start your application flow.

  The sandbox key can be found here:

https://groups.google.com/forum/#!topic/feedly-cloud/egtlxAO6TsQ

  Hope this helps.

-- 

David Chatenay

Feedly

--
You received this message because you are subscribed to the Google Groups "Feedly Cloud" group.
To unsubscribe from this group and stop receiving emails from it, send an email to feedly-cloud...@googlegroups.com.
To post to this group, send email to feedly...@googlegroups.com.
Visit this group at http://groups.google.com/group/feedly-cloud.
To view this discussion on the web visit https://groups.google.com/d/msgid/feedly-cloud/872f6251-16df-4248-aa18-42a980ca70c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dennis Effing]

Hi David,
thanks for your fast response, you cleared up some stuff I had in my mind but I still have two follow-up questions:

1. After logging in via the webview, I get a code from the send redirect which I can use to retrieve an access token as described here https://developer.feedly.com/v3/auth/ in the "Exchanging a code for a refresh token and an access token"?

2. What I don't quite understand is the "Authenticating a user and obtaining a code" section. How does this comply with the login via webview? In this section I don't see any user information and therefore don't know which feeds I could retrieve after authenticating this way.

Regards,
Dennis

[Dennis Effing]

[David Chatenay]

  Hi Dennis,

1. That is correct. Be aware: the code has a limited lifespan (<5 minutes), so if you do this step manually at first, the token might expire before you get it right :)

2. The access token identifies the user who logged in. It needs to be passed it in the "Authorization" header to access other APIs (http://developer.feedly.com/v3/#authentication). For example, to query the list of feeds a user has:

GET /v3/subscriptions

Authorization: OAuth [user's access token]

Once the access token expires (1 week), you can generate a new one (http://developer.feedly.com/v3/auth/#using-a-refresh-token). So it is recommended to persist the refresh token in your app. Otherwise, you will have to ask the user to login every time the access token expires.

-- 

David Chatenay

Feedly

--

You received this message because you are subscribed to the Google Groups "Feedly Cloud" group.
To unsubscribe from this group and stop receiving emails from it, send an email to feedly-cloud...@googlegroups.com.
To post to this group, send email to feedly...@googlegroups.com.
Visit this group at http://groups.google.com/group/feedly-cloud.

To view this discussion on the web visit https://groups.google.com/d/msgid/feedly-cloud/eec40026-7bce-444e-9862-5b90d6ea7e4b%40googlegroups.com.

[thomasag...@gmail.com]

I am using the Feedly Sandbox API. I have already obtained an OAuth code and Access Token for the client. When I request http://sandbox.feedly.com/v3/profile, I get back all the user profile information. However, when I request http://sandbox.feedly.com/v3/subscriptions, I get an empty array, when I am sure that the user (me) has several feeds they are subscribed to.

What is the reason for this? Access to a user's subscriptions is the most important use of the Feedly API - without it, the whole API seems a lot less useful.

Do I need a developer account for this? If so, how do I obtain those keys?

Thank you for the help!

Best,
Tom

[Edwin Khodabakchian]

Hi Thomas,

Sandbox and the main cloud have a different database. Sandbox is just sample / dummy data to help development.

To get access to the main cloud, you can use a developer token (limited to 250 requests) or submit your app for review and approval.

-Edwin

> --
> You received this message because you are subscribed to the Google Groups "Feedly Cloud" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to feedly-cloud...@googlegroups.com.
> To post to this group, send email to feedly...@googlegroups.com.

> Visit this group at https://groups.google.com/group/feedly-cloud.
> To view this discussion on the web visit https://groups.google.com/d/msgid/feedly-cloud/1f2e9da1-568b-4748-bdcf-b2827f80cd47%40googlegroups.com.

[ds89...@gmail.com]

Hi Edwin,

I recently signed up for the pro account and was able to get the access_token, refresh_token and also the userid. Question is what do I do with this? We have built the app which needs client id, secret. This is not sandbox so the sandbox id/sercret are not working. what do i use instead?

Thanks,
Dino

[ds89...@gmail.com]

Hi guys, still no reply on this.
I have to say that for developers looking to build critical applications on top of this API, such response is kinda shitty. If you do not provide support, you might as well shut down this forum as it will save a tonne of time for people like us. Do send me a note when you have done though because for now we are dumping Feedly.

Cheers
Dustor

[david]

  Hi Dustor,

  Your comments are duly noted.

  For the record, if you think that a 3-day response time (including a weekend!) is a long time, I've got some bad news for you...

  I'm not sure how to answer your question, since you declined to provide information about what you are trying to do...

  A good starting point is to look at the subscriptions API, which will return the list of categories and feeds in your account:

https://developer.feedly.com/v3/subscriptions/

  You can use these ids to get (new) articles, using the streams API:

https://developer.feedly.com/v3/streams/

  If you have a Feedly pro account, you can also search through your feeds:

https://developer.feedly.com/v3/search/#search-the-content-of-a-stream

  The access token needs to be passed in the "Authorization:" header in requests, as detailed here:

https://developer.feedly.com/cloud/#authentication

  And you can find a list of resource ids here:

https://developer.feedly.com/cloud/#resource-ids

  Developer access tokens expire after one month. After that, the server will return an HTTP/401 response back. To generate a new access token with your refresh token, see here:

https://developer.feedly.com/v3/auth/#refreshing-an-access-token

  (use "feedlydev" for the client_id and client_secret; these are standard OAuth2 API calls).

  Hope this helps. Good luck,

-- 

David Chatenay

Feedly

[ds89...@gmail.com]

On Wednesday, April 22, 2015 at 2:24:43 PM UTC+5:30, Dennis Effing wrote:

Hi David,

Thanks for coming back and noting the comments.

And yes, a 3 day response time is WAY-too-long(weekend or not) for a company looking to build a product off an API. Some of us are commercial developers trying to build a business and I for one would not want to embarrass myself in front of MY customers giving them the lame excuse of weekend etc. I charge them and I am obliged to respond in time(less than 1 CALENDAR day). I would happily pay for something a bit more serious and where support is more responsive but the way it is setup currently it is a sureshot NO THANKS. Bad news I guess?

Secondly, I am not sure about what sort of people post on this group but for a change, we can all read English. And for anyone who can read English to simply come back and paste documentation links is well..kinda plonkish! Read here to what I asked.
.....
Hi Edwin,

I recently signed up for the pro account and was able to get the access_token, refresh_token and also the userid. Question is what do I do with this? We have built the app which needs client id, secret. This is not sandbox so the sandbox id/sercret are not working. what do i use instead?

........

Thirdly, when someone starts to 'review' apps before giving approval it is a big red flag anyway for any commercially focused developer to consider taking the risk. What if you go on a vaccation or start doing something else for a living in the meantime? We have put in all this effort and we are kinda stuck then..NO THANKS again

Dustor.

[David Chatenay]

  Hi,

  I'm sorry we're unable to meet your expectations. In my experience, few companies provide a one-hour turnaround time on their public API forums.

  I read your question, but it doesn't describe what you are trying to build. I gave my best shot at providing basic help, but it's hard to give good pointers unless I get an idea of what you are trying to build.

  Regarding commercial service, if you send us a description of the SLA you need, the number of users and/or API calls you expect, we can make a proposal. Feedly has been around for 10 years, so we're not going away.

  Best regards,

-- 

David Chatenay

Feedly

--
You received this message because you are subscribed to the Google Groups "Feedly Cloud" group.

To unsubscribe from this group and stop receiving emails from it, send an email to feedly-cloud+unsubscribe@googlegroups.com.

To post to this group, send email to feedly...@googlegroups.com.
Visit this group at https://groups.google.com/group/feedly-cloud.

To view this discussion on the web visit https://groups.google.com/d/msgid/feedly-cloud/ff52d2b2-3819-482b-ba07-d69d5f7e61e4%40googlegroups.com.

[Amit Kr.]

Hi David,

1. 3 days is not one hour.
   
2. I dont know what else to explain about what we are trying to build. Actually now we have abandoned Feedly but when we WERE, it was simply trying to pull feeds from a personal(pro) account. The links you provided were out of ignorance, yes. Because there is no way if you had read the question would you have replied with those links. I do not know why you have that particular link anyway. Specially this - https://developer.feedly.com/v3/developer/ It is outright stupid I have to say. And I do not know any developer who can make sense of this one pager along with the userid/access token/refresh token that you provide to get feeds. Not sure what is so hard to understand about this
3. Lastly, it is 8th of March today and more than 5 days since an application to get a live client id was submitted. That is definitely more than an hour

The fine print is that I see too much risk in investing time and energy with such a part-time, amateurish setup. Thanks for your help so far though but we would not be using you.

Best,

Dustor

[david]

  There's no need to be rude.

  The developer token help page is part of a collection of pages that explain how to use the Feedly API. Have you read the others? They explain how to use the tokens, and any developer familiar with OAuth2 will recognize the pattern.

  The developer access token is specifically designed for the use case you just described ("pull feeds from a personal(pro) account"). The first paragraph on that page states:

"It can be used to experiment with APIs on the live environment without implementing the full OAuth integration; or to build personal applications that interact with your personal live feedly account."

  The special client_id and client_secret to renew developer access tokens is provided in that page as well.

  There is no need to request a client_id or a client_secret for this, unless you are trying to build an application that can be used by other Feedly users. And we do not grant API keys automatically anymore, so you'll need to explain what your application does and how it uses the API.

  I'll make sure to include the guidelines in the developer website as well, to correct assumptions about API access.

  Best regards,

-- 

David Chatenay

Feedly

[ds89...@gmail.com]

On Friday, March 9, 2018 at 1:45:21 AM UTC+5:30, david wrote:
>   There's no need to be rude.
>   The developer token help page is part of a collection of pages that explain how to use the Feedly API. Have you read the others? They explain how to use the tokens, and any developer familiar with OAuth2 will recognize the pattern.
>   The developer access token is specifically designed for the use case you just described ("pull feeds from a personal(pro) account"). The first paragraph on that page states:
>
>
>
> "It can be used to experiment with APIs on the live environment without implementing the full OAuth integration; or to build personal applications that interact with your personal live feedly account."
>
>
>   The special client_id and client_secret to renew developer access tokens is provided in that page as well.
>   There is no need to request a client_id or a client_secret for this, unless you are trying to build an application that can be used by other Feedly users. And we do not grant API keys automatically anymore, so you'll need to explain what your application does and how it uses the API.
>   I'll make sure to include the guidelines in the developer website as well, to correct assumptions about API access.
>   Best regards,
>
>
> -- 
> David Chatenay
> Feedly
>
>
>
>
> On Thursday, March 8, 2018 at 5:01:19 AM UTC-8, Amit Kr. wrote:
>
> Hi David,
>
> 3 days is not one hour.

> I dont know what else to explain about what we are trying to build. Actually now we have abandoned Feedly but when we WERE, it was simply trying to pull feeds from a personal(pro) account. The links you provided were out of ignorance, yes. Because there is no way if you had read the question would you have replied with those links. I do not know why you have that particular link anyway. Specially this - https://developer.feedly.com/v3/developer/ It is outright stupid I have to say. And I do not know any developer who can make sense of this one pager along with the userid/access token/refresh token that you provide to get feeds. Not sure what is so hard to understand about thisLastly, it is 8th of March today and more than 5 days since an application to get a live client id was submitted. That is definitely more than an hour

Not sure what you are calling rude?
Saying that 3 days is not 1 hr.?
Telling you off for 'more trouble on the way'?
Or simply calling out a poorly documented guide?
Or telling you off for sleeping on a request for client_id/secret? In all likelihood you have not seen it as there has been no response for the past 6 days on that.

Notwithstanding all this, it is outright stupid for anyone to waste time building a commercial app off this api. Users are required to have a pro account anyway to be able to use the API so in the unlikely event of someone's business collapsing because they can not access feedly via api, we will simply ask them to go get a developer token with clear disclaimers that we can not guarantee timely support for feedly api

[ds89...@gmail.com]

On Friday, March 9, 2018 at 1:45:21 AM UTC+5:30, david wrote:

>   There's no need to be rude.
>   The developer token help page is part of a collection of pages that explain how to use the Feedly API. Have you read the others? They explain how to use the tokens, and any developer familiar with OAuth2 will recognize the pattern.
>   The developer access token is specifically designed for the use case you just described ("pull feeds from a personal(pro) account"). The first paragraph on that page states:
>
>
>
> "It can be used to experiment with APIs on the live environment without implementing the full OAuth integration; or to build personal applications that interact with your personal live feedly account."
>
>
>   The special client_id and client_secret to renew developer access tokens is provided in that page as well.
>   There is no need to request a client_id or a client_secret for this, unless you are trying to build an application that can be used by other Feedly users. And we do not grant API keys automatically anymore, so you'll need to explain what your application does and how it uses the API.
>   I'll make sure to include the guidelines in the developer website as well, to correct assumptions about API access.
>   Best regards,
>
>
> -- 
> David Chatenay
> Feedly
>
>
>
>
> On Thursday, March 8, 2018 at 5:01:19 AM UTC-8, Amit Kr. wrote:
>
> Hi David,
>
> 3 days is not one hour.

> I dont know what else to explain about what we are trying to build. Actually now we have abandoned Feedly but when we WERE, it was simply trying to pull feeds from a personal(pro) account. The links you provided were out of ignorance, yes. Because there is no way if you had read the question would you have replied with those links. I do not know why you have that particular link anyway. Specially this - https://developer.feedly.com/v3/developer/ It is outright stupid I have to say. And I do not know any developer who can make sense of this one pager along with the userid/access token/refresh token that you provide to get feeds. Not sure what is so hard to understand about thisLastly, it is 8th of March today and more than 5 days since an application to get a live client id was submitted. That is definitely more than an hour

And if users can not use their developer tokens with our product, we will just encourage them to dump feedly and use alternatives

[Amrit Sanjeev]

Hi , 

I am third party developer myself and its the same set of documentation that most of us have used to build the fully functioning commercial applications that are in prod at the moment. You must understand that the documentation here provided by the feedly team is informational not instructional and theres nothing wrong with that approach. It might not be perfect but my personal experience with the team so far has been that they try their best to help if u raise a concern. 

I understand that some of your expectations are not met here but still If there are concerns that you have which can be addressed only by feedly team please reach out to them directly.  Please avoid being abrasive on open forums like this . It doesn't reflect well on anyone . 

Hopefully your concerns are resolved quickly . 

regards, 

Amrit 

--

You received this message because you are subscribed to the Google Groups "Feedly Cloud" group.

To unsubscribe from this group and stop receiving emails from it, send an email to feedly-cloud...@googlegroups.com.

To post to this group, send email to feedly...@googlegroups.com.
Visit this group at https://groups.google.com/group/feedly-cloud.

To view this discussion on the web visit https://groups.google.com/d/msgid/feedly-cloud/3211b57f-90bf-428d-9d66-7bcbd62b8dc0%40googlegroups.com.

[Dustor]

On Friday, March 9, 2018 at 11:07:20 AM UTC+5:30, Amrit Sanjeev wrote:
> Hi , 
>
>
> I am third party developer myself and its the same set of documentation that most of us have used to build the fully functioning commercial applications that are in prod at the moment. You must understand that the documentation here provided by the feedly team is informational not instructional and theres nothing wrong with that approach. It might not be perfect but my personal experience with the team so far has been that they try their best to help if u raise a concern. 
>
>
>
> I understand that some of your expectations are not met here but still If there are concerns that you have which can be addressed only by feedly team please reach out to them directly.  Please avoid being abrasive on open forums like this . It doesn't reflect well on anyone . 
>
>
> Hopefully your concerns are resolved quickly . 
>
> regards, 
>
>
>
> Amrit 
>
>
>
> On Fri, Mar 9, 2018 at 1:45 AM david <da...@feedly.com> wrote:
>
>
>   There's no need to be rude.
>   The developer token help page is part of a collection of pages that explain how to use the Feedly API. Have you read the others? They explain how to use the tokens, and any developer familiar with OAuth2 will recognize the pattern.
>   The developer access token is specifically designed for the use case you just described ("pull feeds from a personal(pro) account"). The first paragraph on that page states:
>
>
>
> "It can be used to experiment with APIs on the live environment without implementing the full OAuth integration; or to build personal applications that interact with your personal live feedly account."
>
>
>   The special client_id and client_secret to renew developer access tokens is provided in that page as well.
>   There is no need to request a client_id or a client_secret for this, unless you are trying to build an application that can be used by other Feedly users. And we do not grant API keys automatically anymore, so you'll need to explain what your application does and how it uses the API.
>   I'll make sure to include the guidelines in the developer website as well, to correct assumptions about API access.
>   Best regards,
>
>
> -- 
> David Chatenay
> Feedly
>
>
>
>
> On Thursday, March 8, 2018 at 5:01:19 AM UTC-8, Amit Kr. wrote:
>
> Hi David,
>
> 3 days is not one hour.

> I dont know what else to explain about what we are trying to build. Actually now we have abandoned Feedly but when we WERE, it was simply trying to pull feeds from a personal(pro) account. The links you provided were out of ignorance, yes. Because there is no way if you had read the question would you have replied with those links. I do not know why you have that particular link anyway. Specially this - https://developer.feedly.com/v3/developer/ It is outright stupid I have to say. And I do not know any developer who can make sense of this one pager along with the userid/access token/refresh token that you provide to get feeds. Not sure what is so hard to understand about thisLastly, it is 8th of March today and more than 5 days since an application to get a live client id was submitted. That is definitely more than an hour

Actually, we have just decided to dump Feedly altogether. We have not heard back from them about our live credentials and for bizzare(most likely lazy and lethargic) reasons, the test environment does not let you test with arbitrary callbacks. And since we are not building some jooky-poky hello world application, it means that we are going to have to go back to David et. al for 'permission'. And that is not happening if we want results in time.

[ds89...@gmail.com]

On Friday, March 9, 2018 at 11:07:20 AM UTC+5:30, Amrit Sanjeev wrote:

> Hi , 
>
>
> I am third party developer myself and its the same set of documentation that most of us have used to build the fully functioning commercial applications that are in prod at the moment. You must understand that the documentation here provided by the feedly team is informational not instructional and theres nothing wrong with that approach. It might not be perfect but my personal experience with the team so far has been that they try their best to help if u raise a concern. 
>
>
>
> I understand that some of your expectations are not met here but still If there are concerns that you have which can be addressed only by feedly team please reach out to them directly.  Please avoid being abrasive on open forums like this . It doesn't reflect well on anyone . 
>
>
> Hopefully your concerns are resolved quickly . 
>
> regards, 
>
>
>
> Amrit 
>
>
>
> On Fri, Mar 9, 2018 at 1:45 AM david <da...@feedly.com> wrote:
>
>
>   There's no need to be rude.
>   The developer token help page is part of a collection of pages that explain how to use the Feedly API. Have you read the others? They explain how to use the tokens, and any developer familiar with OAuth2 will recognize the pattern.
>   The developer access token is specifically designed for the use case you just described ("pull feeds from a personal(pro) account"). The first paragraph on that page states:
>
>
>
> "It can be used to experiment with APIs on the live environment without implementing the full OAuth integration; or to build personal applications that interact with your personal live feedly account."
>
>
>   The special client_id and client_secret to renew developer access tokens is provided in that page as well.
>   There is no need to request a client_id or a client_secret for this, unless you are trying to build an application that can be used by other Feedly users. And we do not grant API keys automatically anymore, so you'll need to explain what your application does and how it uses the API.
>   I'll make sure to include the guidelines in the developer website as well, to correct assumptions about API access.
>   Best regards,
>
>
> -- 
> David Chatenay
> Feedly
>
>
>
>
> On Thursday, March 8, 2018 at 5:01:19 AM UTC-8, Amit Kr. wrote:
>
> Hi David,
>
> 3 days is not one hour.

> I dont know what else to explain about what we are trying to build. Actually now we have abandoned Feedly but when we WERE, it was simply trying to pull feeds from a personal(pro) account. The links you provided were out of ignorance, yes. Because there is no way if you had read the question would you have replied with those links. I do not know why you have that particular link anyway. Specially this - https://developer.feedly.com/v3/developer/ It is outright stupid I have to say. And I do not know any developer who can make sense of this one pager along with the userid/access token/refresh token that you provide to get feeds. Not sure what is so hard to understand about thisLastly, it is 8th of March today and more than 5 days since an application to get a live client id was submitted. That is definitely more than an hour

Hi Amrit,

Thanks for speaking out but unfortunately I do not agree with your assessment here. We are on this forum because the Feedly team has asked us to be. They have not said, talk to 'sup...@feedly.com' etc. And for that reason, I am not going to have any direct communication with them.
Depending upon what you have built or were trying to, you may have had the time to wait for people to come back from vacation etc. but that is totally unacceptable to us. Also it is not even so much about the documentation itself, but the really poor nature of support(if you call it that) in responding to developer queries.

It is irrelevant, what your experience is Amrit, ours has not been good. Unfortunately though, this is the only place to speak out so if you feel offended, please feel free to duck out.

Cheers,
Dustor

[david]

  Calling someone "outright stupid" and calling us an "amateurish setup", implying that I'm lazy or sleeping on the job is rude. 

  Even if there is some truth in that, these comments are not helpful.

  I have not seen your request for a client_id/secret. It is possible that you used an old email address that is not monitored anymore. Which is why I deleted a thread in this forum...

  Requiring a Feedly Pro account is one of 3 possible cases to get a client id, as explained in the sandbox message:

1. If you are building an innovative consumer application using Feedly (innovative because of a new platform or UI), we will grant you a license and help you distribute your solution. The key here is around innovation.
   
2. If you are building a business application and integrating with Feedly to enable your customers access their Feedly content, we require a Feedly Pro or a Feedly Teams license for each customer. This is what we are doing with Buffer, IFTTT, Zapier, etc. 
3. Otherwise, we are offering a new Feedly as a paid API package that allows you to integrate feedly into your internal or private applications or websites, as a feed and content management solution. Please contact ed...@feedly.com for details.

  If none of these work for you, we're open to hear your suggestions. If you make a compelling case, we can work something out.

  As for timely support, I'm striving to help as much as I can, as quickly as I can. But I'm also the lead engineer building the APIs, so my time, like yours, is limited.

  Best regards,

-- 

David Chatenay

Feedly

[ds89...@gmail.com]

It is rude to state the obvious? If you think so then...wait...' there is a lot more trouble on the way'. So far I have just been polite.
You have a lousy setup not worthy of time and investment from anyone remotely serious about making money. Sure, preachers who have a fulltime job telling others what to do and 'manage relations' might have time for you, I do not. I have said that time and again.
The reason being not only that your documentation is crap, but also, you have a lousy approach to collaboration. It is STUPID. Who are you to be 'approving' apps when the data actually belongs to the customer? Even if you do have some element of interest in this, the fact that you can not find (let along action) requests only points to the danger and risk of collaborating with you.

What is rude is trivializing support queries and calling 3 days one hour. It is also stupid. Outright stupid. So you get what you ask for.

[ds89...@gmail.com]

On Wednesday, April 22, 2015 at 2:24:43 PM UTC+5:30, Dennis Effing wrote:

Moreover, having all development work point to localhost is just lazy. Reflects your part-time approach to coding or perhaps lack of qualified resources to implement a simply solution to allow serious developers to test things without making stupid changes to their environments. Not every one runs useless hello world apps and calls them 'successful production integrations'. For anyone remote familiar with enterprise development, it should not be hard to figure out how much time would be wasted in changing a setup to point to a hardcoded url for testing. It is STUPID.