[Osr-101] Getting abstract (or: defining Neutron's
target abstraction level)
Andreas Wuest
awuest at student.ethz.ch
Fri Sep 8 21:04:07 CEST 2006
Hi Gregor
On 8.9.2006 17:45 Uhr, Gregor Imboden wrote:
> Am Freitag, 8. September 2006 17:26 schrieb Gregor Imboden:
>> Am Freitag, 8. September 2006 16:30 schrieb Andreas Wuest:
>>> 1. Completely independent of the application layer protocol.
>>>
>>> 2. Dependent on two-way communication capable application layer
>>> protocols. Independent of specific Neutron endpoints.
>>>
>>> 3. Dependent on two-way communication capable application layer
>>> protocols. Dependent on specific Neutron endpoints.
>>>
>>> 4. Dependent on the HTTP application layer protocol.
>>>
>>> I, for one, believe that we should aim for abstraction level 2. The
>>> current specification is a mixture of levels 3 and 4.
>> But if we would go to straight to the application layer we couldn't
>> implement Neutron let's say as an Apache HTTPD module (actually we could
>> but whe had to mess with socket/io directly and would loose the whole HTTP
>> abstraction), i think that would hinder a lot of people from implementing
>> neutron.
>
> Darn, ignore my statements about socket-io and apache, it would work perfectly
> as a cgi when we use the HTTP protocol...
So, does this change your opinion on the target abstraction level, or
would you still vote for level 4?
>> I would prefer level 4. without the dependency on Neutron specific
>> endpoints.
--
Kind regards,
Andi
More information about the Osr-101
mailing list