when de-serializing a link, it should check if the namespace atom was added to the xml or if the link contains an namespace attribute to the atom specification, otherwise its a simple link attribute

Restfulie allows you to throw UnsupportedMediaTypeError and render 415

http://www.rubyinside.com/ and br version

Based on asyn invocation, support generic timeout

all raises were not tested... nasty

When requesting something already in cache, it should use a local cache to avoid the request at all.

If your type does not extend ActiveRecord::Base, it should have its attributes setted while deserializing.

there should be automatic filtering for transition methods were one would check for the objects possible transition state.

create a tutorial and break the main docs in 3 parts

The following code should work:
payment = compra.check_payment_info do |res|
Payment.from_xml res.body
end

suggest on docs that if you have only one media type, you can easily do it without tokamak

Allow the client to configure the behavior of the application when receiving any 300 range status code. This configuration should be done for each HTTP method, indicating the status code, for example:

config.auto_follows = [
  { :post => [301, 307] },
  { :get   => [301, 307] } 
]

rake build should build the gem
rake install should locally install it

Allows you to register custom unmarshallers on the server side and use them to read the request encoded entity.

based on your models, you can generate your json without any extra cnfiguration. all fields will be included.

To... have less bugs on to_hash and from_xml
As... guilherme
I want to... update MattPulver's with its last version from his blog

while making a get request it should automatically load the json object as it does with the xml counterpart

Re-write active support on top of Restfulie with restfulie capabilities

render -> restful should invoke to_xml with controller

Still, the only available media type to use on the server is atom. The server must offer other media types to serialize.

Link headers received on the client side should be made accessible as usual links

The request and response stack should be split in two. Take a look on the Java implementation which is better written in this way :)

the restfulie restbuy project requires human interaction on localhost:3000/admin
instead of waiting it shoul do a straight request tothe admin interface to settle the payment and then check again!

The problem appeared after updating from 0.4 to 0.6 when requesting a resource from a xml representation.

• Server response code: 406 - Not Acceptable
• Client request accept header: application/xml
• Controller's code

Firing up console and running "Restfulie.at('http://localhost:3000/orders/1').get" gives me back an Hashi::CustomHash object with resource's html representation. A solution proposed by Guilherme that fixed the problem for show action was to use render_resource instead of respond_to. I haven't updated the rest of controller's code to use render_created and render_collection to find out what happens.

Don't know if it helps but trying to fix the bug I've found out that commenting lines below this one makes respond_to work properly again.

not only refresh, but also "show"

hi there,

thanks for your great set of useful hypermedia gems. we will release a geodatabase service and wrapper gem soon, utilizing restfulie.

since we are developing in 1.9.2 and rails3 we encountered the warning:

DEPRECATION WARNING: exempt_from_layout is no longer needed, because layouts in Rails 3 are restricted to the content-type of the template that was rendered.

/lib/tokamak/hook/rails.rb:73

In Rails3 it works fine just without the line so there could simply be added a condition to exclude this in a rails 3 gem stack.

keep up the great work!

kind regards,
Frederik

When executing a self request which returns a 304, return the model itself

After a request, the client would prefer to get only the raw response body instead of an object representation.

Therefore, Restfulie::Client must give this option to the client.

The client still don't implement these operations (on the new structured version).

Link it to a wiki page that mentions and links to all github projects and their issues

After a request, the client would access the request object to check any of its properties.

Instead of creating every route needed to implement access to resource links, the server should offer a route DSL to be used in routes.rb file that will generate all routes needed by a resource. Something similar with map.resources for example.

There is no suggestion yet for DSL syntax.

the POST method should be sent without parameters, just the body itself

transforming it into a gem will make our development / test process easier

we should use jeweler / gemcutter

Link relations should be optionally rendered as link headers

the server side code provides a method named can_"state"? but it still not implemented. implement it, make it work through the order server side example and document it

Rails already offer a way to set a media type parameter parsing scheme, as the documentation shows:

 # Assign a new param parser to a new content type
ActionController::Base.param_parsers['application/atom+xml'] = Proc.new do |data| 
    node = REXML::Document.new(post) 
   { node.root.name => node.root }
end

Therefore, Restfulie must implement a way to enable the user to set specific media types and also support the common ones.

Rails already support XML, JSON and YAML. This feature should also include atom+xml.

Update the readme file in the root directory

All the old site uris should redirect to the wiki

due to the use of from/to xml/json one has to extend from ActiveRecord::Base. That should be optional

while serializing, there should be an option to save the atom namespace definition in the xml header, so the code is smaller.

to_xml method requires the controller, doc it

deploy rubyforge

Any Link collection (Links class) should have a method called refresh, which is a shortcut for .self.get.

pick a feature/anything.rb and implement unit test for it

if a rails object is given and no config, render all attributes by default

After receiving a 201, Restfulie should follow the Location header with a GET request.

Create a Restfulie.at shortcut to Restfulie::Client::EntryPoint.at

if the error is 405, correctly raise and notify