difference between session and cokkies in ruby on rails

It looks like your question is about the difference between sessions and cookies in Ruby on Rails, which is not directly related to the content presented at WWDC. However, I can provide some information about sessions as discussed in the context of WWDC.

Sessions in WWDC Context

In the session titled "What’s new in location authorization" at WWDC 2024, sessions are discussed in the context of CoreLocation services. Here are some key points:

1. Session Objects: CL service session objects are used to inform CoreLocation about the app's needs. They help manage location authorization and ensure that the app can continue to function correctly even when it is backgrounded or terminated.

2. Implicit vs. Explicit Sessions: Implicit sessions are automatically managed by CoreLocation when live updates or events are iterated. Explicit sessions, on the other hand, are manually created by the developer to handle specific authorization needs, such as requiring full accuracy or always authorization.

3. Session Lifecycle: The lifecycle of a session is tied to the user-facing features of the app. For example, if a feature like recording an exercise track continues in the background, the session should also continue to assert the app's interest in its authorization goal.

4. Layering Sessions: Different components of an app can create their own service sessions as needed, without having to coordinate with each other. This makes it easier to manage complex features that may have different authorization requirements.

For more detailed information, you can refer to the session chapter markers:

• What’s new in location authorization (Session lifecycle)

Sessions and Cookies in Ruby on Rails

While this is not covered in the WWDC content, here's a brief overview:

• Sessions: In Ruby on Rails, sessions are used to store data that you want to persist across multiple requests from the same user. This data is stored on the server-side, and a session ID is stored in a cookie on the client-side to identify the session.

• Cookies: Cookies are small pieces of data stored on the client-side. They can be used to store user preferences, authentication tokens, and other data that needs to persist between requests. Unlike sessions, cookies are directly accessible by the client.

If you have any more questions about the content presented at WWDC, feel free to ask!