why memcached is called a object cache

[Prateek Mathur]

On 12/19/06, Prateek Mathur <mathurprateek at gmail.com> wrote:
>
> I think to make it object-oriented, you would need to the cache to store
> and understand an "object model" of a particular programming language, so
> that you could seamlessly retrieve objects and stores objects in that
> programming language. Memcached right now without being object oriented, can
> support many clients of any programming language.
> The memcached server could be running on C/c++ code and have clients of
> perl,java,.net etc...Since it stores objects in bytes and doesnt have to
> understand what the object is.And using network socket programming under
> the hood , it could read and write that object.
> If it has to be object oriented, then it would have to understand the
> object model of different types of languages for which it has to
> support.So I think this could be one reason why it isnt..
>
> Thanks
> Prateek.
>
> On 12/19/06, zhang Jackie <jackieict at gmail.com> wrote:
> >
> > hi,everyone
> >    As we all know, memcached is a object cache. But why it is not called
> > object-oriented cache?
> > any reply is appreciated!
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.danga.com/pipermail/memcached/attachments/20061219/3318c2a1/attachment.html