What platforms does Rebex consider "legacy"?
Legacy platforms are platforms that are no longer covered by our Standard Support but have not yet reached End of Life. Legacy Editions of Rebex components targeting these platforms are available as separate products.
What is the difference between a Legacy Edition and standard edition?
- Standard editions of Rebex components only include binaries and support for platforms covered by Standard Support.
- Legacy Editions only include binaries and support for specific legacy platforms (such as .NET CF 3.5/3.9).
// synchronize using SNTP protocol
Ntp.SynchronizeSystemClock("test.rebex.net");
// synchronize using Time protocol
Time.SynchronizeSystemClock("test.rebex.net");
// synchronize using Daytime protocol
Daytime.SynchronizeSystemClock("test.rebex.net");
Using SNTP, Time and Daytime protocols, your application can determine the exact time from Internet time servers.
Why Rebex Time?
Get server time
Retrieve current time using SNTP, Time or Daytime protocol.
Time synchronization
Synchronize your local machine clock with a time server. It takes only one line of code - and works on Windows and Linux.
Multiple time protocols
More features
- Specify protocol version 3 or 4 in SNTP
- Choose between TCP or UDP in Time and Daytime
- Get NTP server stratum
- Access additional NTP response fields
- More features
Licensing and support
- Royalty free redistribution.
- Includes 1 year support contract.
- Includes all new versions released during 1 year.
Featured samples
-
Windows Forms Time
Windows Forms Time application demonstrates how to work with a time server. -
Time Client - iOS NTP client
A simple NTP client for Xamarin.iOS. -
Time Client - Android NTP client
A simple NTP client for Xamarin.Android. -
TimeSynchronize
The sample asks a time server for time difference and uses the answer to update time on the local machine.
Tags: Rebex, Internet and Networking, .NET, Rebex Time Legacy CF Platforms