- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 103 for design (0.03 sec)
-
docs/smb3-features/06-witness-protocol-design.md
# Witness Protocol Feature - Detailed Design Document ## 1. Overview The SMB Witness Protocol enables rapid notification of resource changes in a clustered file server environment. It provides fast failover capabilities by allowing clients to register for notifications about server node availability, share movement, and other critical cluster events. ## 2. Protocol Specification Reference - **MS-SWN**: Service Witness Protocol Specification
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 02:53:50 UTC 2025 - 42K bytes - Viewed (0) -
docs/smb3-features/04-directory-leasing-design.md
# Directory Leasing Feature - Detailed Design Document ## 1. Overview Directory leasing extends the SMB3 lease concept to directories, enabling client-side caching of directory metadata and change notifications. This significantly improves performance for applications that frequently enumerate directories or monitor directory changes. ## 2. Protocol Specification Reference - **MS-SMB2 Section 2.2.13.2.12**: SMB2_CREATE_REQUEST_LEASE_V2 for directories
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 02:53:50 UTC 2025 - 36.2K bytes - Viewed (0) -
docs/smb3-features/01-smb3-lease-design.md
# SMB3 Lease Feature - Detailed Design Document ## 1. Overview SMB3 leases provide a client caching mechanism that replaces the traditional oplock mechanism. Leases enable better performance through client-side caching while maintaining cache coherency across multiple clients. ## 2. Protocol Specification Reference - **MS-SMB2 Section 2.2.13**: SMB2 CREATE Request with Lease Context - **MS-SMB2 Section 2.2.14**: SMB2 CREATE Response with Lease State
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 02:53:50 UTC 2025 - 22K bytes - Viewed (0) -
docs/smb3-features/02-persistent-handles-design.md
# Persistent Handles Feature - Detailed Design Document ## 1. Overview Persistent handles (also known as durable handles) allow SMB3 connections to survive network disconnections, server reboots, and client reconnections. This feature is critical for enterprise reliability and seamless failover scenarios. ## 2. Protocol Specification Reference - **MS-SMB2 Section 2.2.13.2.3**: SMB2_CREATE_DURABLE_HANDLE_REQUEST
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 02:53:50 UTC 2025 - 31.6K bytes - Viewed (0) -
docs/smb3-features/03-multi-channel-design.md
# Multi-Channel Feature - Detailed Design Document ## 1. Overview SMB3 Multi-Channel enables the use of multiple network connections between client and server, providing increased throughput, network fault tolerance, and automatic failover capabilities. This feature aggregates bandwidth across multiple NICs and provides seamless failover when network paths fail. ## 2. Protocol Specification Reference
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 02:53:50 UTC 2025 - 39.6K bytes - Viewed (0) -
docs/smb3-features/05-rdma-smb-direct-design.md
# RDMA (SMB Direct) Feature - Detailed Design Document ## 1. Overview SMB Direct enables high-performance data transfer using Remote Direct Memory Access (RDMA) technology. This provides ultra-low latency and high bandwidth data transfer by bypassing the traditional TCP/IP stack and allowing direct memory-to-memory transfers between client and server. ## 2. Protocol Specification Reference - **MS-SMBD**: SMB2 Remote Direct Memory Access (RDMA) Transport Protocol
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 02:53:50 UTC 2025 - 35.9K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/app/web/admin/design/FileAccessForm.java
* governing permissions and limitations under the License. */ package org.codelibs.fess.app.web.admin.design; import org.lastaflute.web.validation.Required; /** * Form class for file access operations in the admin design interface. * This form handles file name validation for accessing design files. */ public class FileAccessForm { /** The name of the file to access (required) */ @RequiredRegistered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Thu Jul 17 08:28:31 UTC 2025 - 1.2K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/app/web/admin/design/EditForm.java
public EditForm() { // Default constructor } /** * The name of the design file being edited. * This specifies which template or design file to modify. */ public String fileName; /** * The content of the design file. * This contains the actual template code, CSS, or other design content * that will be saved to the specified file. */ public String content;
Registered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Thu Jul 17 08:28:31 UTC 2025 - 1.3K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/app/web/admin/design/DesignForm.java
*/ package org.codelibs.fess.app.web.admin.design; import org.lastaflute.web.ruts.multipart.MultipartFormFile; /** * Form class for design file management in the admin interface. * Handles upload and management of design templates and CSS files. */ public class DesignForm { /** * Creates a new instance of DesignForm. * This constructor initializes the form for design file managementRegistered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Thu Jul 17 08:28:31 UTC 2025 - 1.5K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/app/web/admin/design/UploadForm.java
*/ package org.codelibs.fess.app.web.admin.design; import org.lastaflute.web.ruts.multipart.MultipartFormFile; import org.lastaflute.web.validation.Required; import jakarta.validation.constraints.Pattern; /** * Form for uploading design files to customize the appearance of the Fess search interface. * This form is used in the admin interface to upload CSS, JSP, and other design-related files
Registered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Thu Jul 17 08:28:31 UTC 2025 - 1.8K bytes - Viewed (0)