Re: Did ebXML Help Accelerate the Web Services Evolution?

["Ashish Rathod" <a_thesis@yahoo.com>]

Duane:

 

Thanks for your comments.

 

It certainly looks impressive. I will refer to the url for updates.

 

Ashish :)

Duane Nickull <dnickull@adobe.com> wrote:

Ashid:

My pleasure. Longhorn's architecture is divided into four main components:

The Base Operating System
Presentation (code named "Avalon")
Data Layer
Communication (code named "Indigo")

Most security functions are handled at the base O/S layer. Within the
O/S layer, there is a hardware abstraction layer that talks to the lower
level BIOS. The main kernel is built upon this.

Some security is handled within the network library classes. This
component contains protocol specific security plus MS extensions to it.
There is a native internet firewall (say good bye to firewall software
as third party windows ware), several lower level protocols and a
protocol filter. I am not certain but I believe the security model for
communications seems to be a methodology where the filter blocks
everything by default except for approved types (A good model IMO, used
by NT currently).

Other security is handled by the layer built upon the kernel and is your
stock O/S type security (RWX permissions, sharing and other standards
functions). Many of these lower level security functions will be used by
the higher level components such as presentation. It will probably be
possible to prevent certain data components from being used or even
viewed by actors with inappropriate permissions. Audit trails may also
be possible.

The .NET framework security model also plays an important role. This
protects your content (code and data) from being misused or damaged by
other processes. This is accomplished by enforcing security
restrictions on managed code.
The Admins security policy governs all code. All trusted code can be
required to have a digital signature (approved by MS). Trust is also
based on where the code comes from. Once granted, security enforces
permissions that control what code is (and by not being granted, what
code is not) allowed to do.

Not sure how the .NET and Longhorn framework will handle policy
declarations with respect to code written in languages other than C#, Vb
etc.

A lot of stuff is available on line but it is all subject to change.
Historically, Longhorn has been a moving target so visit the MS site
often to look for updates.

Duane




Ashish Rathod wrote:

> Duane:
>
> What type of security will be included in "Longhorn"?What are your
> thoughts?
>
> -researcher
>
> Duane Nickull <DNICKULL@ADOBE.COM>wrote:
>
> BTW - Microsoft's new direction is to embed SOA within their
> proprietary O/S
>
> "The "Longhorn" communications subsystem (code-named "Indigo")
> infrastructure enables you to create a wide variety of
> applications. You
> can create something as simple as a chat application that operates
> between two peers on an intranet, and as complex as a scalable Web
> service for millions of users."
>
> It is very impressive technology. Read more:
> http://longhorn.msdn.microsoft.com/
>
> Duane
>
> Brian Repko wrote:
>
> >
> > ebXML folks:
> >
> > Sorry, I wrote that VERY poorly. What I meant was that the
> > ebXML spec designers were already of a mindset to take on
> > web services when they (web services) came around. I realize
> > (since I've been a silent stalker of this list forever) that ebXML
> > predates the web services specs.
> >
> > You all - "were already there" to migrate to web services.
> >
> > Sorry about the confusion. Duane - I love that quote. I'm still
> > not sure the IBM/Microsoft (GXA) folks see it that way. Even
> > with Sun there is reluctance to add the ebXML specs to the
> > scope of related JSRs (BPSS on the JBI spec - I might have that
> > name wrong - I'm writing from memory).
> >
> > Brian
> >
> > _________________________________________________________________
> > Find a broadband plan that fits. Great local deals on high-speed
> > Internet access.
> >
> https://broadband.msn.com/?pgmarket=en-us/go/onm00200360ave/direct/01/
> >
> >
> > The ebxml-dev list is sponsored by OASIS The
> > list archives are at http://lists.ebxml.org/archives/ebxml-dev/
> > To subscribe or unsubscribe from this list use the subscription
> > manager:
> >
>
> --
> Senior Standards Strategist
> Adobe Systems, Inc.
> http://www.adobe.com
>
>
>
>
> The ebxml-dev list is sponsored by OASIS The
> list archives are at http://lists.ebxml.org/archives/ebxml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager:
>
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Yahoo! Finance Tax Center - File
> online. File on time.


--
Senior Standards Strategist
Adobe Systems, Inc.
http://www.adobe.com




The ebxml-dev list is sponsored by OASIS The
list archives are at http://lists.ebxml.org/archives/ebxml-dev/
To subscribe or unsubscribe from this list use the subscription manager:

---

Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.