hi, The advantage of first is that we will gonna have all the styles at a single place and no need to call for the default page from other places as we will gonna do in the second method. Here but we have to apply the constraints on the default entries and not on other entries. On other hand in second point we will have a unify table with same functionality for all the entries but we have to call the default styles which will be at different place.

Thanks,

Prakhar Joshi DA-IICT,Gandhinagar

On Mon, Mar 16, 2015 at 8:48 AM, Stephen J. Turnbull <stephen@xemacs.org> wrote:

...

hi, I am Prakhar Joshi (irc name :- _pjoshi). I have few things to discuss about the storage of new styles for the list that will be created

...

rest API. I think we should create a separate table for the list styles and there we can add the entries for the newly created styles in those

...

Now we have to work around for storing these default styles in the database. Here what I think is we can do it in 2 ways :- 1) We have two default entries in the table and can only have "GET" request for these two and "GET"/"POST" request for rest of the entries in the table. 2) We can have these 2 default styles out of the table and these 2 can be called as they are now from their places in the web interface

prakhar joshi writes: through tables. directly.

What are the advantages and disadvanatages of the two approaches as far as you are concerned?

Steve