会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明授权
    • Methods and apparatus providing a categorical approach to strongly typed component management
    • 为强类型组件管理提供分类方法的方法和设备
    • US07788677B1
    • 2010-08-31
    • US11325172
    • 2006-01-04
    • Ruben MichelStanislav SosnovskyRichard Francis Cormier
    • Ruben MichelStanislav SosnovskyRichard Francis Cormier
    • G06F9/44G06F9/45
    • G06F8/30H04L67/00H04L67/34
    • A code generator generates component controllers by receiving, as input, an identity of a component and identities of dependent components of the component and applying a categorical-based generator that applies at least one morphism to generate at least one component controller to manage both collocated and remote access to the dependent components of the component in a strongly typed manner. Application of the categorical based generator includes generating at least one service-component controller for controlling service components that, during operation, are instantiated upon component server initialization to provide services to other components during component server operation and generating at least one session-component controller for controlling session components instantiated, utilized for services during a session, and terminated as needed by other components.
    • 代码生成器通过接收作为输入的组件的身份和组件的依赖组件的标识并应用基于分类的生成器来生成组件控制器,所述生成器应用至少一个态射以生成至少一个组件控制器来管理并置和 以强类型方式远程访问组件的依赖组件。 基于分类的生成器的应用包括生成用于控制服务组件的至少一个服务组件控制器,所述服务组件在操作期间在组件服务器初始化时被实例化,以在组件服务器操作期间向其他组件提供服务,并且生成至少一个会话组件控制器 控制会话组件被实例化,在会话期间用于服务,并根据其他组件的需要终止。
    • 2. 发明授权
    • Methods and apparatus for a timer event service infrastructure
    • 定时器事件服务基础设施的方法和装置
    • US07552446B1
    • 2009-06-23
    • US10750413
    • 2003-12-31
    • Stanislav SosnovskyRuben MichelIlya Liubovich
    • Stanislav SosnovskyRuben MichelIlya Liubovich
    • G06F3/00G06F9/44G06F9/46G06F13/00G06F1/00G06F1/04G06F1/14
    • G06F1/14G06F9/4825G06F9/542G06F2209/543
    • Complex software systems often require time-based processing, such as delayed or periodic timer event handling. A timer service provides an Application Programming Interface (API) for managing timers, and therefore provides a developer abstraction for representing time-based processing. In operation, the timer service infrastructure employs a plurality of timer events, each having a corresponding timer handler, in which each of the timer events is associated with a generic timer reference, employed by a timer interface. The generic reference, therefore, may refer to any of the plurality of timers. The timer service may disable, or passivate modules including subscribers having timer handlers without disrupting timer continuity and invocation. Upon timer expiration, the timer service enables modules having subscribers to the timer. The timer service therefore seamlessly enables inactive modules upon timer expiration. Further, the common generic timer reference avoids timer event specific stubs and references related to specific classes, which tend to complicate deployment.
    • 复杂的软件系统通常需要基于时间的处理,例如延迟或周期性的定时器事件处理。 定时器服务提供了一个用于管理定时器的应用程序编程接口(API),因此提供了一种用于表示基于时间的处理的开发人员抽象。 在操作中,定时器服务基础设施采用多个定时器事件,每个定时器事件具有对应的定时器处理器,其中定时器事件中的每一个与定时器接口采用的通用定时器参考相关联。 因此,通用引用可以指多个定时器中的任何一个。 定时器服务可以禁用或钝化包括具有定时器处理器的用户的模块,而不会中断定时器连续性和调用。 定时器到期后,定时器服务启用具有定时器订户的模块。 因此,定时器服务在定时器到期后无缝地启用非活动模块。 此外,常见的通用计时器引用避免了定时器事件特定的存根和与特定类相关的引用,这往往会使部署复杂化。
    • 3. 发明授权
    • Techniques using an API for aspect weaving
    • 使用API​​进行纵向编织的技术
    • US08418192B1
    • 2013-04-09
    • US13200675
    • 2011-09-28
    • Stanislav SosnovskyRichard F. CormierSylvia J. MartinShailendra S. BistPrem K. Singh
    • Stanislav SosnovskyRichard F. CormierSylvia J. MartinShailendra S. BistPrem K. Singh
    • G06F13/00
    • G06F9/54G06F8/316G06F2209/541
    • Described are techniques for executing an application. The application includes a plurality of partitions including business logic and one or more aspects. A first registration interface of an application programming interface is defined for registering a code entity and associated input and output parameters. A provider of a first aspect of the application is registered using the first registration interface to define the provider as a callback invoked from other code of the application programming interface that performs aspect weaving. The provider includes a first code entity and a first data entity of the first aspect. A second code entity of the business logic is executed that performs a call to the other code performing aspect weaving to obtain a second data entity of the business logic. The other code performing aspect weaving is executed and performs a callback to the provider of the first aspect.
    • 描述了用于执行应用程序的技术。 应用程序包括多个分区,包括业务逻辑和一个或多个方面。 定义应用程序编程接口的第一注册接口,用于注册代码实体和相关的输入和输出参数。 使用第一注册接口来注册应用的第一方面的提供者,以将提供者定义为从执行方面编织的应用编程接口的其他代码调用的回调。 提供者包括第一方面的第一代码实体和第一数据实体。 执行业务逻辑的第二代码实体,执行对执行方面编织的其他代码的调用以获得业务逻辑的第二数据实体。 执行方面编织的其他代码被执行并对第一方面的提供者执行回调。
    • 5. 发明授权
    • Methods and apparatus providing an event service infrastructure
    • 提供事件服务基础设施的方法和设备
    • US07559065B1
    • 2009-07-07
    • US10750227
    • 2003-12-31
    • Stanislav SosnovskyRuben MichelIlya Liubovich
    • Stanislav SosnovskyRuben MichelIlya Liubovich
    • G06F3/00G06F9/44G06F9/46G06F13/00
    • G06F9/542G06F2209/544
    • In a conventional managed information environment network, event notification mechanisms typically monitor the various nodes and interconnections in the network. In particular configurations of the invention, an event service infrastructure allows an event, or class definition, to define the event and related event data. Invocation of the event includes only the event specific class definition. The infrastructure transparently processes the subsequent reporting and invocation of the appropriate event handler. The event handler, corresponding to the event definition, performs remedial and responsive processing of the event. A developer need only develop entities to subscribe to an event to identify the appropriate handler, and publish the event with any related event data upon detection. Each particular event avoids extraneous event definitions and associated files, thereby relieving the developer from unrelated events and allowing focus on the pertinent events. A detecting software entity initiates event handling by publishing the event, upon which the event service identifies and invokes each subscriber entity for performing the event handler associated with the event.
    • 在传统的托管信息环境网络中,事件通知机制通常监视网络中的各种节点和互连。 在本发明的特定配置中,事件服务基础设施允许事件或类定义来定义事件和相关的事件数据。 事件的调用仅包括事件特定的类定义。 基础架构透明地处理随后的报告和调用相应的事件处理程序。 对应于事件定义的事件处理程序对事件进行补救和响应处理。 开发人员只需要开发实体来订阅一个事件来识别适当的处理程序,并在检测到时发布具有任何相关事件数据的事件。 每个特定事件都避免了无关的事件定义和相关的文件,从而缓解了开发人员的不相关事件,并且可以专注于相关事件。 检测软件实体通过发布事件来发起事件处理,事件服务识别并调用每个订户实体来执行与事件相关联的事件处理器。
    • 6. 发明授权
    • Methods and apparatus for administering software modules in a storage area network management application
    • 在存储区域网络管理应用中管理软件模块的方法和装置
    • US07275098B1
    • 2007-09-25
    • US10608608
    • 2003-06-27
    • Andrew S. BecherStanislav Sosnovsky
    • Andrew S. BecherStanislav Sosnovsky
    • G06F15/173G06F9/445
    • G06F8/61G06F3/0607G06F3/0632G06F3/067
    • System, methods and apparatus operate a module server to service a plurality of different storage area network management modules that each provides a respective type of management functionality for elements operating within a storage area network. The system operates an administration module in conjunction with a module sever. The administration module provides a plurality of module administration interfaces that are software interfaces that can be remotely invoked to administer the plurality of different storage area network management modules. The system receives a remote invocation of at least one of the plurality of module administration interfaces and applies module administration functionality associated with the at least one remotely invoked module administration interface to remotely administer at least one of the storage area network management modules serviced by the module server. By decoupling the administration from the module server, the module server does not need to be shut down to perform module administration and is a less complicated and smaller software process.
    • 系统,方法和装置操作模块服务器来服务多个不同的存储区域网络管理模块,每个不同的存储区域网络管理模块为在存储区域网络内操作的元件提供相应类型的管理功能。 该系统与模块服务器一起运行管理模块。 管理模块提供多个模块管理接口,它们是可被远程调用以管理多个不同存储区域网络管理模块的软件接口。 所述系统接收所述多个模块管理接口中的至少一个的远程调用,并且应用与所述至少一个远程调用的模块管理接口相关联的模块管理功能,以远程管理由所述模块服务的所述存储区域网络管理模块中的至少一个 服务器。 通过将管理与模块服务器分离,模块服务器不需要关闭以执行模块管理,并且是较不复杂和较小的软件过程。
    • 8. 发明授权
    • System and methods for defining a software build
    • 用于定义软件构建的系统和方法
    • US07640533B1
    • 2009-12-29
    • US11094773
    • 2005-03-30
    • Dan LotteroStanislav SosnovskyRuben MichelRichard Francis CormierIlya Liubovich
    • Dan LotteroStanislav SosnovskyRuben MichelRichard Francis CormierIlya Liubovich
    • G06F9/45
    • G06F8/71G06F8/10
    • A software build framework includes and architecture to identify software components including sets of classes, or objects, and categorizes the objects into layers in the component. A set of build rules identifies allowable dependencies between the component layers among the same and other components in the system, as well as external entities such as off the shelf (OTS) and third party vendor products outside the development control. The build mechanism enumerates a set of dependencies for each of the components, and an enforcer analyzes the dependencies to identify dependencies in violation of the rules. The enforcer separates the compile time and runtime inheritance paths to detect indirect monolithic inheritance. In this manner, dependency rules define an efficient and optimal architecture which lends itself well to modifications, timely builds and deliverable releases, and enforces the dependency rules at compile time so as to avoid generating an obsolete or suspect build.
    • 软件构建框架包括和架构,用于识别包括类或对象的软件组件,并将对象分类为组件中的层。 一组构建规则确定系统中相同和其他组件之间的组件层之间的允许依赖关系,以及外部实体(如现成的OTS)和开发控制之外的第三方供应商产品。 构建机制枚举了每个组件的一组依赖关系,执行者分析依赖关系以识别违反规则的依赖关系。 执行者分离编译时和运行时继承路径,以检测间接的单片继承。 以这种方式,依赖规则定义了一种有效和最优的体系结构,可以很好地适应修改,及时构建和可交付的版本,并在编译时强制实施依赖关系规则,以避免产生过时或可疑的构建。
    • 10. 发明授权
    • Methods and apparatus for providing extensible lightweight services in a data storage environment
    • 在数据存储环境中提供可扩展的轻量级服务的方法和装置
    • US07590714B1
    • 2009-09-15
    • US10750334
    • 2003-12-31
    • Stanislav SosnovskyRuben MichelIlya Liubovich
    • Stanislav SosnovskyRuben MichelIlya Liubovich
    • G06F15/173
    • G06F9/542
    • Conventional development architectures for software system development employ varied invocation and triggering mechanisms for various objects and processes, such as services. Integrating new services tends to impose substantial changes in multiple code objects, requires retroactive testing, and increases the risk of failure. A services architecture in which users of a service seamlessly employ a respective service using only the objects, classes, and entities germane to the service usage provides interprocess module and service entity invocation. Extraneous definitions and functions, such as housekeeping relating to activation and passivation, location (module or component) of the service, and memory allocation, are removed from the user view. The architecture provides for automatic activation in the event components for providing the service have been passivated. Invocation requests are mapped across modules to the appropriate service entities. In this manner, the services architecture provides a seamless user view of the service by handling extraneous functions and allowing the service user to focus on the subscriber rather than the service implementation detail.
    • 用于软件系统开发的传统开发架构为各种对象和过程(如服务)采用不同的调用和触发机制。 集成新服务往往会对多个代码对象进行实质性更改,需要追溯测试,并增加失败的风险。 服务架构,其中服务的用户无缝地使用仅使用与服务使用密切相关的对象,类和实体的相应服务来提供进程间模块和服务实体调用。 从用户视图中删除了与激活和钝化,服务的位置(模块或组件)以及内存分配有关的内部定义和功能。 该架构提供了事件中的自动激活,用于提供服务的组件已被钝化。 调用请求通过模块映射到相应的服务实体。 以这种方式,服务架构通过处理无关功能并允许服务用户专注于用户而不是服务实现细节来提供服务的无缝用户视图。