Annotating SCO's Appellate Reply Brief

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Annotating SCO's Appellate Reply Brief
# 1  
Old 11-22-2010
Annotating SCO's Appellate Reply Brief

We've been quietly working on a project to annotate SCO's Reply Brief [PDF] in its appeal, noting every statement that we think isn't accurate and providing whatever evidence we can find to support the annotation. Now that we've got the ball rolling, would you like to help us finish? If so, feel free to do so in your comments, which I can then add to the project. When we're all done, I'll leave an update saying so, and meanwhile this is a work in progress.
Here's SCO's appeal brief, its initial filing, and here's Novell's opposition brief, which you may wish to have handy too. I've put our annotations in blue and indented to make them easier to find.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
CosNotifyChannelAdmin_StructuredProxyPushSupplier(3erl)      Erlang Module Definition	   CosNotifyChannelAdmin_StructuredProxyPushSupplier(3erl)

NAME
CosNotifyChannelAdmin_StructuredProxyPushSupplier - This module implements the OMG CosNotifyChannelAdmin::StructuredProxyPushSupplier interface. DESCRIPTION
To get access to the record definitions for the structures use: -include_lib("cosNotification/include/*.hrl"). This module also exports the functions described in: * CosNotifyComm_NotifySubscribe * CosNotification_QoSAdmin * CosNotifyFilter_FilterAdmin * CosNotifyChannelAdmin_ProxySupplier EXPORTS
connect_structured_push_consumer(StructuredProxyPushSupplier, PushConsumer) -> Reply Types StructuredProxyPushSupplier = #objref PushConsumer = #objref Reply = ok | {'EXCEPTION', #'CosEventChannelAdmin_AlreadyConnected'{}} | {'EXCEPTION', #'CosEventChannelAdmin_TypeError'{}} This operation connects a PushConsumer to the target object. If a connection already exists or the function push_structured_event is not supported by the client object an exception is raised. suspend_connection(StructuredProxyPushSupplier) -> Reply Types StructuredProxyPushSupplier = #objref Reply = ok | {'EXCEPTION', #'CosNotifyChannelAdmin_ConnectionAlreadyInactive'{}} | {'EXCEPTION', #'CosNotifyChannelAdmin_Not- Connected'{}} This operation suspends the connection with the target object. If no connection exists or the connection already is suspended an exception is raised. resume_connection(StructuredProxyPushSupplier) -> Reply Types StructuredProxyPullConsumer = #objref Reply = ok | {'EXCEPTION', #'CosNotifyChannelAdmin_ConnectionAlreadyInactive'{}} | {'EXCEPTION', #'CosNotifyChannelAdmin_Not- Connected'{}} If the connection with the target object have been suspended this function must be used to resume the connection. If no client have been connected or the connection is active an exception is raised. disconnect_structured_push_supplier(StructuredProxyPushSupplier) -> ok Types StructuredProxyPushSupplier = #objref This operation cause the target object to close the connection and terminate. Ericsson AB cosNotification 1.1.16 CosNotifyChannelAdmin_StructuredProxyPushSupplier(3erl)