Struct NEAppProxyTCPFlow

Source

pub struct NEAppProxyTCPFlow { /* private fields */ }

Expand description

The NEAppProxyTCPFlow class declares the programmatic interface of an object that is used by NEAppProxyProvider implementations to proxy the payload of TCP connections.

NEAppProxyTCPFlow is part of NetworkExtension.framework

Instances of this class are thread safe.

Implementations§

Source §

impl NEAppProxyTCPFlow

Source

pub unsafe fn readDataWithCompletionHandler( &self, completion_handler: &DynBlock<dyn Fn(mut NSData, mut NSError)>, )

Available on crate feature block2 only.

Read data from the flow.

Parameter completionHandler: A block that will be executed when some data is read from the flow. The block is passed either the data that was read or a non-nil error if an error occurred. If data has a length of 0 then no data can be subsequently read from the flow. The completion handler is only called for the single read operation that was initiated by calling this method. If the caller wants to read more data then it should call this method again to schedule another read operation and another execution of the completion handler block.

Source

pub unsafe fn writeData_withCompletionHandler( &self, data: &NSData, completion_handler: &DynBlock<dyn Fn(*mut NSError)>, )

Available on crate feature block2 only.

Write data to the flow.

Parameter data: The data to write.

Parameter completionHandler: A block that will be executed when the data is written into the associated socket’s receive buffer. The caller should use this callback as an indication that it is possible to write more data to the flow without using up excessive buffer memory. If an error occurs while writing the data then a non-nil NSError object is passed to the block.

Source

pub unsafe fn remoteEndpoint(&self) -> Retained<NWEndpoint>

👎Deprecated

An NWEndpoint object containing information about the intended remote endpoint of the flow.

Source §

impl NEAppProxyTCPFlow

Methods declared on superclass NSObject.

Source

pub unsafe fn init(this: Allocated<Self>) -> Retained<Self>

Source

pub unsafe fn new() -> Retained<Self>

Methods from Deref<Target = NEAppProxyFlow>§

Source

pub unsafe fn openWithLocalEndpoint_completionHandler( &self, local_endpoint: Option<&NWHostEndpoint>, completion_handler: &DynBlock<dyn Fn(*mut NSError)>, )

👎Deprecated

Available on crate feature block2 only.

This function is used by an NEProvider implementation to indicate that it is ready to handle flow data.

Parameter localEndpoint: The address and port that should be used as the local endpoint of the socket associated with this flow. If the source application already specified a local endpoint by binding the socket then this parameter is ignored.

Parameter completionHandler: A block that is called when the process of opening flow is complete. A nil value passed to this block indicates that the flow was opened successfully. A non-nil NSError value indicates that the flow failed to open successfully.

Source

pub unsafe fn closeReadWithError(&self, error: Option<&NSError>)

This function is used by an NEProvider implementation to indicate that it does not want to receive any more data from the flow.

Parameter error: An error in NEAppProxyErrorDomain that should be passed to the flow’s source application.

Source

pub unsafe fn closeWriteWithError(&self, error: Option<&NSError>)

This functions is used by an NEProvider implementation to indicate that it does not have any more data to write to the flow.

Parameter error: An error in NEAppProxyErrorDomain that should be passed to the flow’s source application.

Source

pub unsafe fn metaData(&self) -> Retained<NEFlowMetaData>

An NEFlowMetaData object containing meta data for the flow.

Source

pub unsafe fn remoteHostname(&self) -> Option<Retained<NSString>>

If the flow was created by passing a hostname to a “connect by name” API such as NSURLSession or Network.framework, this property is set to the remote hostname.

Source

pub unsafe fn isBound(&self) -> bool

YES if the flow was bound by the application to a specific interface (contained in the networkInterface property), NO otherwise.

Methods from Deref<Target = NSObject>§

Source

pub fn doesNotRecognizeSelector(&self, sel: Sel) -> !

Handle messages the object doesn’t recognize.

See Apple’s documentation for details.

Methods from Deref<Target = AnyObject>§

Source

pub fn class(&self) -> &'static AnyClass

Dynamically find the class of this object.

§Panics

May panic if the object is invalid (which may be the case for objects returned from unavailable init/new methods).

§Example

Check that an instance of NSObject has the precise class NSObject.

use objc2::ClassType;
use objc2::runtime::NSObject;

let obj = NSObject::new();
assert_eq!(obj.class(), NSObject::class());

Source

pub unsafe fn get_ivar<T>(&self, name: &str) -> &T
where T: Encode,

👎Deprecated: this is difficult to use correctly, use Ivar::load instead.

Use Ivar::load instead.

§Safety

The object must have an instance variable with the given name, and it must be of type T.

See Ivar::load_ptr for details surrounding this.

Source

pub fn downcast_ref<T>(&self) -> Option<&T>
where T: DowncastTarget,

Attempt to downcast the object to a class of type T.

This is the reference-variant. Use Retained::downcast if you want to convert a retained object to another type.

§Mutable classes

Some classes have immutable and mutable variants, such as NSString and NSMutableString.

When some Objective-C API signature says it gives you an immutable class, it generally expects you to not mutate that, even though it may technically be mutable “under the hood”.

So using this method to convert a NSString to a NSMutableString, while not unsound, is generally frowned upon unless you created the string yourself, or the API explicitly documents the string to be mutable.

See Apple’s documentation on mutability and on isKindOfClass: for more details.

§Generic classes

Objective-C generics are called “lightweight generics”, and that’s because they aren’t exposed in the runtime. This makes it impossible to safely downcast to generic collections, so this is disallowed by this method.

You can, however, safely downcast to generic collections where all the type-parameters are AnyObject.

§Panics

This works internally by calling isKindOfClass:. That means that the object must have the instance method of that name, and an exception will be thrown (if CoreFoundation is linked) or the process will abort if that is not the case. In the vast majority of cases, you don’t need to worry about this, since both root objects NSObject and NSProxy implement this method.

§Examples

Cast an NSString back and forth from NSObject.

use objc2::rc::Retained;
use objc2_foundation::{NSObject, NSString};

let obj: Retained<NSObject> = NSString::new().into_super();
let string = obj.downcast_ref::<NSString>().unwrap();
// Or with `downcast`, if we do not need the object afterwards
let string = obj.downcast::<NSString>().unwrap();

Try (and fail) to cast an NSObject to an NSString.

use objc2_foundation::{NSObject, NSString};

let obj = NSObject::new();
assert!(obj.downcast_ref::<NSString>().is_none());

Try to cast to an array of strings.

use objc2_foundation::{NSArray, NSObject, NSString};

let arr = NSArray::from_retained_slice(&[NSObject::new()]);
// This is invalid and doesn't type check.
let arr = arr.downcast_ref::<NSArray<NSString>>();

This fails to compile, since it would require enumerating over the array to ensure that each element is of the desired type, which is a performance pitfall.

Downcast when processing each element instead.

use objc2_foundation::{NSArray, NSObject, NSString};

let arr = NSArray::from_retained_slice(&[NSObject::new()]);

for elem in arr {
    if let Some(data) = elem.downcast_ref::<NSString>() {
        // handle `data`
    }
}