I agree with Mike - I think cookies should be standard. However, my reason is less because 'users' need cookies regularly, but because a huge number of plug-ins and widgets do. State-management is becoming a 'requirement' for many widgets, so having a standard cookie API *built-in* is superior to a having a dependancy on a cookie plug- in. My own widgets use cookies - to avoid a dependancy for something so basic, I add my own cookie code to *each* widget. This works, but having $.cookie built-in would be preferable.
The code/bytes required for basic cookie handling is neglible. In fact, some extra functionality could even be added to enhance its use for state-management and it would still be miniscule. It would be best in the jQuery core because there are thousands of plugins that use cookies. But failing this, the jQuery UI core should include it so every ui-widget has a *standard cookie API* to use. It seems odd to create a comprehensive widget library where many of widgets have a dependancy on a tiny, non-ui plug-in. /Kevin On Aug 21, 8:41 am, diogobaeder <diogobae...@gmail.com> wrote: > Agreed. Cookies are rarely used, if compared with other > functionalities that jQuery supports today. Also, as constantly > commented here at this discussion list, it's always good to avoid > putting more funcionalities into the core, if they can (an makes sense > that they) stay outside of it, for us not to turn it into a heavy- > weighted library. > > Mike, what is the problem of having a plugin for cookies, instead of > in the core, in your point of view? > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
