base_url field in specification

11 views
Skip to first unread message

Aitor ATuin

unread,
Aug 22, 2013, 4:17:52 PM8/22/13
to spore...@googlegroups.com
Hi, currently im working on a spore implementation in scala and i cant understand very well the reason for base_url be optional. What url should be use in case base_url is not provided?

Greets.

Stéphane Raux

unread,
Aug 23, 2013, 4:14:42 AM8/23/13
to spore...@googlegroups.com
Hi,

The base_url can also be defined at the instanciation of a spore client.
It allows to use the same spore specification for a service that can
be hosted on several servers (eg. when switching between a dev server
and a prod server).

In current spore implementations, the base_url defined at the
instanciation of the client overrides the one defined in the
specification (if any).

Best,

Stéphane


2013/8/22 Aitor ATuin <aitor....@gmail.com>:
> --
> You received this message because you are subscribed to the Google Groups
> "SPORE" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to spore-rest+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

Aitor ATuin

unread,
Aug 23, 2013, 6:39:44 PM8/23/13
to spore...@googlegroups.com
Hi Stéphane, i missed the option for provide a base_url at client instantiation, i will add support for it. Anyway I'm wrapping every value into a kind of Either monad to manage errors, currently i use the method base_url if provided, if not the one defined at specification is used, if neither of two define the field, then an error inside the monad is returned. Now i will add support to provide a base_url at client instantiation.

Greets.
Reply all
Reply to author
Forward
0 new messages