[Registry-dev] Product name and color theme

[Davanum Srinivas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

+1 to using "application/atom+xml;type=collection" to create the hierarchy!

- -- dims

Paul Fremantle wrote:
> Chathura and I have looked at APP closely. That is the plan we are going
> with.
> 
> The only extension/non-specified issue we believe we need to deal with
> is how to create a new collection within a collection.
> 
> My proposal is to treat a collection like any other "non-atom-entry"
> item. So I propose that to create a new atom collection, the APP client
> should POST a <collection> with content-type:
> application/atom+xml;type=collection
> 
> The spec explicitly says this behaviour is undefined: see 9.6
> "In particular, what happens on POSTing an Atom Feed Document to a
> Collection using the "application/atom+xml" media type is undefined."
> 
> However I read this as meaning we can do what we like. However, we
> aren't doing anything that isn't completely logical. It seems to me that
> the behavior I'm suggesting is *exactly* what would happen if we treat
> atom collections like any other media type.
> 
> Apart from that I think we can just use APP as described.
> 
> Paul
> 
> 
> 
> Davanum Srinivas wrote:
> Hmm...Can we please design the REST API first? :) Has anyone other
> than me looked at APP yet?
> 
> -- dims
> 
> Glen Daniels wrote:
>>>> I agree that we shouldn't make this the official name of the product.
>>>> However I think it would make a fantastic thing to note in a blog entry
>>>> when we release it!
>>>>
>>>> --Glen
>>>>
>>>> Sanjiva Weerawarana wrote:
>>>>> Sorry, I'm -1 on it .. REST is just starting to fall down the
>>>>> precipice heading towards the trough of disillusionment.
>>>>>
>>>>> Let's not get carried away- we use what we find useful and stop at
>>>>> that ..
>>>>>
>>>>> Sanjiva.
>>>>>
>>>>> Ruwan Linton wrote:
>>>>>> Since we need to emphasis on RESTFull behavior how about this,
>>>>>>
>>>>>> "WSO2 REgiSTry"
>>>>>>
>>>>>> Well the name is the same, but different representation.
>>>>>>
>>>>>> Thanks,
>>>>>> Ruwan
>>>>>>
>>>>>> Glen Daniels wrote:
>>>>>>> Sanjiva Weerawarana wrote:
>>>>>>>> With products with boring names like WSO2 WSAS, WSO2 WSF, WSO2 ESB,
>>>>>>>> WSO2 MS we cannot suddenly call the newest one WSO2 Moxie or WSO2
>>>>>>>> Foxy.
>>>>>>> :)
>>>>>>>
>>>>>>>> I like R3 .. RESTful Registry & Repository to but I'm also keen
>>>>>>>> that we maintain consistency.
>>>>>>>>
>>>>>>>> So maybe it'll have to be WSO2 Registry after all ...
>>>>>>> Within the constraints that we've got (which I personally take issue
>>>>>>> with but I'll just note that and move right along), I'm fine with
>>>>>>> that name.
>>>>>>>
>>>>>>> --Glen
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Registry-dev mailing list
>>>>>>> Registry-dev at wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Registry-dev mailing list
>>>>>> Registry-dev at wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>>>>>
>>>> _______________________________________________
>>>> Registry-dev mailing list
>>>> Registry-dev at wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>>>
> 
> 
>>
_______________________________________________
Registry-dev mailing list
Registry-dev at wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>

- --
Davanum Srinivas (dims at wso2.com)
Director, Customer Engagements, WSO2 (http://wso2.com)
Yahoo IM: dims Cell/Mobile: +1 (508) 415 7509
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFG+QwhgNg6eWEDv1kRAtsyAKCwoKvVoR9mJRQot/vknbMOeAQC7ACfcjZG
JYBs718D4ldVLt5lmJ82PCc=
=BhM/
-----END PGP SIGNATURE-----