Friday, 21 September 2012

It's almost here! New version of Advanced Rest Client

Hi all!

I'd like to inform you that new version of the application is almost ready :)
It took over 3 months but the application was written from scratch. Now it can do a lot more than current version. Thanks for all who submit an issue on http://code.google.com/p/chrome-rest-client/issues/list and helps me improve application.

Note:
There is a number of new permissions required by the application. See bottom of this post for more info.

Let's start from UI.

New version UI

UI now have more modern look. It is not very different from current version, but devil is in the details. Have you noticed that there is new option in menu?

Projects is a new feature. It helps you organize saved requests and you can easily switch between requests sharing it's parameters. More about projects you can find in my previous post.
Project view
OK, let's make a HTTP request:


Still it is not very different form previous version. But as you can see I've added new section to response view. Now Request Headers are also available in application view. And there is more.
Since now you can overwrite browsers headers that are not available for regular XmlHttpRequest! This mean that you can set User-Agent, Accept and many more headers. It becomes possible since new declarativeWebRequest API in Chrome. And here is the bad news. For today it is only available for Chrome Dev Channel (version 23). It will take about 3 months before it becomes available in stable version. Since then I'll send an update to Web Store but it will be available for version 23+.

Let's go on. Lately someone suggest that application should show redirect chain (issiue 67). Well, here it is:

It will show complete request flow. For each redirect it collects information about received headers, status and information is this redirection comes from cache (f.e. HTTP 301) or not.


I've made some improvements to request form panel. You can "open" url input field and create URL using form:
When you need to encode query parameters just pres "enc" button for this parameter. If you need to encode parameter but replace + with %20 just hold CTRL key.


There are changes in settings section as well. First at all "cookies capture" is no more experimental. Well, it is not working very well right now. Results may vary and you can't rely on it. But since application can show all response headers (even those invisible to the XmlHttpRequest object) you can see cookie data in response panel.
There is no JSON headers settings. This is fixed now and list contain all popular json headers definitions.

Important change for the application is import/export options. Since now export to application server is deprecated and this option will be removed December 1st, 2012.
There are better options for import export. First is export to file. Application will generate json file with projects and requests definitions. You can easily change it's content and send file to collaborators. Thanks to this change you don't need to be worry about data sent to application server.

Next step it to implement Google Drive API to save file directly on your drive. Then the application becomes one of the Google Drive applications.

There is a number of new permissions required by application.

  • webRequest 
    • This is required to observe and analyze traffic - to know when redirect occur and to catch request and response headers 
  • declarativeWebRequest 
    • This is required to modify request headers by XmlHttpRequest (to remove or add headers)
  • background 
  • storage 
    • Chrome provides API for sync data. Application will synchronize some settings like debug and history options.
  • history (not changed) is required by URL widget to provide fill support. While typing an URL it search application's and browser's history. When it find matches it will return it in suggestions list. Browser's history is not stored in application. 
  • <all_urls> (not changed) is required by application to make any request outside application sandbox. 
  • cookies permission has been removed

I hope you like changes and you will like new version of the application. Update will become available in next few weeks. Since then you still can report an issue if you found some :)

Cheers!

Wednesday, 25 July 2012

Little stats :)

I've just check that Advanced Rest Client have great stats :)
According to Google Analytics, daily almost 5 thousand of you are using this application! In last month there was 30 thousands unique users that have opened application! And Chrome Web Store claims that there is 33587 weekly users.
Thanks :)

Tuesday, 17 July 2012

Work on new version in progress... :)

If you're wondering when new version of Rest Client will be available I just wanna let you know that it will happen in next one or two months.
Why so long? - you probably ask. Well, it will be totally new version. Whole application is writing right now from scratch. And this needs time :(
Picture below is showing application's start up flow diagram. That shows how many operations is needed to run the application.



What is new in the application? 
First at all: the projects. If you have more than one endpoint of the same webapplication (developer server, test server, production server, etc) then you will can save WebRequests under one project. When you open project you will be able to quickly switch between endpoints and define which part of URL need to change (either protocol, host, path or params) and to what it should change.

For example you have REST project under http://dev.rest.com/api?key=mydevkey&restOfParams
Then you might want to switch to production server but it's host address is http://myproject.com and there you have different API key. 
By creating a project you can define reference URL address http://dev.rest.com/api?key=mydevkey&restOfParams (you can give it a name, like "dev"). Then, for another endpoint, you'll tell the app that it must change server value and key param when switching between endpoints (to defined values).


Second big change in application is closer integration with chrome extensions API.
Now, you can't set some of headers (like cookie, user, user-agent etc). It's not permitted by XMLHttpRequest spec. Using Chrome API application can change headers just before sending request to server, omitting specification restrictions.

Proposed change is integration with Google Drive. Instead of sending saved requests to application's server (app engine) you'll be able to save it to Google Drive and share it with co-workers. It's safer way for you and cheaper for me ;)

Next change is integration with external extensions. Some of you emailed to me to give them possibility to access to the application via extensions communication system (to run application, to replace results window, etc). I'm working on this and it should be available in next version. 

That's all for now.
I'd like to hear feedback from you! If you have suggestions write to me, please.

Tuesday, 17 April 2012

New version wireframe. Comment what do you think about.

Hi there!
I've started working on new version of Advanced Rest Client.
The big changes will be:

  • replace saved request with "Projects" section. One project can have many request (for example with common parameters but different endpoints)
  • replace Web Databases with Indexed Databases and move some of local storage params to IDB (for better performance)  
  • simplify UI for better user experience
  • and... please, tell me if you want something more to change/add/remove

Look out wireframes and tell me (in comments) what do you thinking about it. It's only two because other views probably will not going to change.

Main page
Selected project


Cheers.

Tuesday, 27 March 2012

Time goes on

Nope, I haven't forgot about my favorite application.
I just changing my job right now and I don't have time to code lately... I read your comments on application profile and reported issues on Google Developers. But I need more time to work wit this. So be patient, report new bugs (if any :) and I will take care of it.

Happy RESTing :)

P.S.
If you curious about my new company it's interactive agency Kalicinscy.com :)

Thursday, 9 February 2012

Applications server version.

Hi,
Lately I worked about application performance. I did a lot of improvements, but it is not a subject of this post.
I like to announce that server side application is working from now at http://chromerestclient.appspot.com/
After you log in you can view all data that you've sent to server and delete it if you need.
On this site you can remove all your data as well (including connection to your Google account).

If you have any suggestions write email to me or create issue ticket at http://code.google.com/p/chrome-rest-client/issues/list

Cheers!

Monday, 23 January 2012

Permissions chage - conclusion

I've noticed that many of You asked me about new permissions in application.
What can I say more? Permission change was noted in applications description and on this blog post.

Application won't send any of your data to any server and I will not use it for any purpose. You can make sure about this by checking source code (http://code.google.com/p/chrome-rest-client/source/browse/#svn%2Ftrunk%2FRestClientApp) or just opening chrome inspector (ctrl + shift + i) and check is any data are send somewhere.


I don't feel like deserve for lower rating just because You can't read :)

Cheers!