Jaxer Extension

[Nathan Smith]

Hi,

I made a small modification to this so it can be used as a Jaxer extension. If you put the file in your local_jaxer/extentions, you can use it with Jaxer.memcached. It's attached. I haven't tested it at all, though, but the concept works (it's used for this.) Cool project, BTW, can't wait to try it out.

Thanks,

Nathan

[Rakesh Pai]

Thanks Nathan. I haven't had the chance to look at the code yet, but
I'll try to incorporate your changes as soon as possible.

However, if this project is not part of the Jaxer family of products,
I'd rather respect the namespace and not try to pollute it. I think
it's the only way to maintain api sanity. So, if all there are any
benefits of making this a Jaxer extension (I don't know about
extensions yet) and if it can be done without modifying the Jaxer
namespace, your changes will be absorbed into the code.

That said, are there any benefits of having this as a Jaxer extension?
Quick google searches only reveal that this is a very new feature, and
the documentation around it is still very sparse.

On 1/23/09, Nathan Smith <nll...@gmail.com> wrote:
> Hi,
>
> I made a small modification to this so it can be used as a Jaxer extension.
> If you put the file in your local_jaxer/extentions, you can use it with
> Jaxer.memcached. It's attached. I haven't tested it at all, though, but the

> concept works (it's used for this <http://nlsmith.com/console/>.) Cool

> project, BTW, can't wait to try it out.
>
> Thanks,
>
> Nathan
>
> >
>

--
Sent from Gmail for mobile | mobile.google.com

Rakesh Pai
Mumbai, India.
rakes...@gmail.com
http://piecesofrakesh.blogspot.com/

[nlloyds]

Rakesh,

A Jaxer extension by design will "pollute" the Jaxer namespace. Here's
how I understand them to work:

You have a local_jaxer/extensions folder. When the Jaxer process
starts it will look in there and attempt to execute any scripts. If
the scripts add properties to the Jaxer object, those properties will
persist for the lifetime of the Jaxer server.

The advantage is that the code for your extension won't have to be
executed on every page request, but will, in effect, become part of
Jaxer. I share your apprehension of adding to objects that aren't
"yours", but something as beneficial as memcached support would
probably be welcomed.

I also don't know too much about the extensions, I'm just an early
adopter and end user like yourself. You may be able to find more
detailed explanations on the Aptana forums.

Thanks,

Nathan

[Rakesh Pai]

Sorry for the delay Nathan.

Your changes have been added to the repository. I've created two separate versions - one to be included as a script src include, and one to be used as a jaxer extension. I've also updated the docs accordingly.

Thanks, and keep the changes coming in!

--